I was wondering, I know how to make a snapshot from SQL passthrough , but can
VB actually modify records(meaning get returned records) from an SQL server or
does the server have to do everything.. A small explanation would be great>

T.I.A.

:)

This seems to be a very popular thread here.  Has anyone thought about
adding a section to the FAQ that covers this topic?  Maybe a few
strategies that cover using VB and SQL Server?  There is really very
little documentation to help someone. I can volunteer some of my time.

/*

   Computing Analyst
   Oak Ridge National Laboratory
   http://www.ornl.gov
*/

says...

If you create a dynaset instead of a snapshot, you can edit records, add
records, etc...

As far as the server doing everything, SQL server does all the IO.  Meaning VB
tells SQL to change some data, then SQL server takes over and actually does the
changes.

I'm not sure this is really that great of an explanation, but if you need more
help, let me know.

The subject line does not seem to match the actual Q, but...

VB submits changes to SQL Server who writes out those changes.  So
technically SQL Server makes the changes, but under VB's direction.

The 'trick' is to know when to do that in client code (ie a ds.Edit) vs a
Server procedure.  Both have advantages, but you *can* design (oops, there
is the D word) the app so that it is a biut dumber and leverage the server
power to do the updates for you.  This tends to speed things up a bit but
it might result in other things that need to be  gotten around.

- Mike

Yes, VB can do this.  The easiest way is to use an attached SQL
Server table through an .mdb.  From the application's standpoint
it will be exactly the same as using an .mdb based table.

Keep two things in mind, though:

1.  You must have a unique index on the table on the sql server
side in order for jet to be able to update the table on sql
server.

2.  There is no easy way through vb 3.0 to update what sql
server/database/table to which a particular attached table
points.