January 23, 2007 at 9:37 am
My environement includes a 3rd party application (Bartender - prints Barcodes) that makes an OLE call to the database. The Bartender application has a stored user & password (SQL Server Authentication) that has access to execute two stored procedures.
The 3rd party application works fine on WinXP but from Win2000 the application keeps bringing up the prompt to SQL (with user and *'d password, and ultimately failing in the data call.
Has anybody else stumbled upon this 'feature' and hopefully have a suggestin?
thanks
daralick
January 23, 2007 at 2:59 pm
Where the name and the password are stored? Could it be that on Windows 2000 computer these values are not configured? What is the front end?
For example, if the app uses ODBC source, it could be that on the Windows 2000 computer it is configured to use SQL Server login while on XP machine it is using Windows authentication. Another example are Excel Pivot Tables that can store or don't store login info based on the checkbox.
Regards,Yelena Varsha
January 29, 2007 at 12:17 pm
MDAC MDAC MDAC...
Person onsite updated the MDAC to the latest version and viola!.
Daryl
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply