Re: different mdac, different sql server behaviour
From: Keith Kratochvil (sqlguy.back2u_at_comcast.net)
Date: 12/22/04
- Next message: jmeyers: "Re: spid locks"
- Previous message: mimorr: "Re: spid locks"
- In reply to: Tony Epton: "different mdac, different sql server behaviour"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 22 Dec 2004 11:22:45 -0600
(1) MDAC Component Checker
http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en
(2) I would guess that you are using the ODBC driver, but I don't know. How
did you set up the link to SQL Server in the first place?
-- Keith <ace join_to ware@iinet.net.au (Tony Epton)> wrote in message news:41c9a201.57817078@news.m.iinet.net.au... > 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
- Next message: jmeyers: "Re: spid locks"
- Previous message: mimorr: "Re: spid locks"
- In reply to: Tony Epton: "different mdac, different sql server behaviour"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
