Different mdac, different SQL server behaviour

T

Tony Epton

I have done a partial conversion of a large MS Access batch processing
program to use a SQL server 2000 back end.
All I have done is move all the access tables in to SQL server and
give them primary keys so that tje Access front end can attach to them
as updateable tables. No pass thru queries or anything that will take
advantage of the SQL facilities.

In my development environment I am running Access 97 on Windows 98.

The client is running Access 97 on Windows XP

I am seeing different behaviour between my environment and the clients
environment - with exactly the same data sitting on the back end SQL
databases and exactly the same Access 97 front end.

I have managed to knock all the bugs out of the program when it runs
in my environment - but in their environment we are still seeing the
dreaded "Record is Deleted" message - seems to occur in some
situations where I use an outer join and attempt to pick up a value
from a field in the non existent record side of the join.

QUESTION - presumably the discrepancies are caused by us running
different versions of MDAC

1) can anyone tell me where I can download that utility that tells you
which version of mdac you are running
2) which part of mdac am I using when access attaches to the SQL back
end but all the work is still being done by the access front end ?

ole db server for Access ? odbc driver for SQL, jet ?

Many thanks
Tony
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top