jeffrey.demulling at usbank.com
jeffrey.demulling at usbank.com
Wed Jun 4 11:41:14 CDT 2003
Since you converted to A2K why not use the power of SQL Server and create stored procedure for your application to use? "Paul M. Jones" <pjones at btl.net> Sent by: accessd-bounces at databaseadvisors.com 06/04/2003 11:29 AM Please respond to accessd To: accessd at databaseadvisors.com cc: Subject: [AccessD] A97 to A2K conversion issues I have an A97 application that connects to SQL Server 2000 via ODBC that has been running for the last couple of years. I recently converted it to A2K. I have since found a lot of quirky things that has led me to rewrite certain parts of my code that functions perfectly well under A97. My latest problem is that I have a fairly complex query that selects information from several other queries. This query now gives me an 'ODBC--called' failed error under A2k even though all the smaller queries that it selects from work ok. I am now thinking I might need to create temporary tables rather than using queries as the source of the final query. Without getting into the details of the various queries, anyone has any ideas on parameters or configurations that can be made with A2K before I take the route of redoing a ton of work? On another note, for anyone planning to do this type of upgrade on Windows 2000 systems, please be sure that they all have SP3 installed. A2K did not work properly on any of the Win2K systems that had SP1 or SP2. Only with SP3 did I get consistency I expected from what was supposed to be a simple upgrade. Paul M. Jones Spire Services Ltd. _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030604/edc04fe3/attachment-0001.html>