Hollis,Virginia
HollisVJ at pgdp.usec.com
Fri Oct 31 08:48:52 CST 2003
Yes, it is a .dsn. The date wasn't changed, but we re-created it anyway, relinked all the tables & it is now working. Another strange thing is that it worked not only on my machine, but a users that was running XP OS. I think someone had to have changed something on the server in IT, this just doesn't 'happen'. -----Original Message----- From: Stuart McLachlan [mailto:stuart at lexacorp.com.pg] Sent: Thursday, October 30, 2003 4:37 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] RE: AllowBreakIntoCode", dbBoolean, False On 30 Oct 2003 at 16:18, Hollis,Virginia wrote: > Something strange has happened to the SQL Server connection. Now keep in > mind - this has been working for months now with no problems, this week > something has changed and I have no clue what happened. > > Somehow the connection has been changed. First change I found, the data was > coming from the development server instead of production. I looked at the > tables and there were all these records with test test as the title. Now it > is requiring a password to SQL Server. I have the ODBC connection to the SQL > Server tables. I relinked the tables, set up a new connection and it is > still not working. Of course IT tells me they have not changed anything, but > they are working on the problem. > What sort of ODBC connection? I'd suspect you are using a File DSN and someone has changed it. (Take a look at the actual DSN file and check it's modified date and owner) -- Lexacorp Ltd http://www.lexacorp.com.pg Information Technology Consultancy, Software Development,System Support. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com