[AccessD] RE: AllowBreakIntoCode", dbBoolean, False

Stuart McLachlan stuart at lexacorp.com.pg
Thu Oct 30 16:37:24 CST 2003


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.





More information about the AccessD mailing list