Returning SQL Server error messages

S

s

I have an Accesss 2002 adp file that connects to SQL Server 2000. We are
now using Access 2003 and I have found that Access does not appear to be
catching errors raised on the server. I used to execute "RunCommand
acCmdSaveRecord" and if there were any errors on the server I would capture
Err number 5000. Under Access 2003 the server side errors do not get passed
to the client.

Any ideas why this is no longer working? Tx.
 

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

Similar Threads

Outlook Desktop (latest) stopped syncing IMAP accpounts from selfowned Mail server. 0
Data provider could not be initialized 1
Connect to SQL Server from A2k 4
Access 2007 can't connect to SQL Server 1
Keeping Access Running Between SQL Server Reboots 3
Access 2000 ADP and SQL Server 2005 2
Slow connection from Access 2003 to SQL Server 2008 1
Upsizing to SQL Server, I lost my forms 1

Top