Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Runtime Interfacing with SQL Server

Status
Not open for further replies.

marshw

MIS
May 24, 2001
8
0
0
US
My company is running a large database stored on an SQL Server, with an Access Front End. We've been encountering some problems which we believe are related to the distinct ways in which Access and SQL Server encode dates. It seems that several users are unable to run certain forms/reports that utilize queries with a date restriction in the WHERE clause. For instance: "WHERE Orders.OrderDate > #5/1/01#". Users running Windows 2000 Professional with Access 2000 remain error-free, while users running the .mde file via Access Runtime on Win 98 machines cannot open said forms/reports. We are unsure that a date formatting conflict issue is the proper diagnosis, but we arrived at this conclusion after observing that the forms/reports load properly until the queries containing date conditions are executed. Of course, SQL queries written for the Access front end appear in regular Access format: dates surrounded by #'s. Access apparently translates these dates into proper, single-quote-surrounded format, before sending a command to the SQL server. Our theory, although unconfirmed, is that when the .mde file is run with full-blown Access, this format conversion is done properly, but that Access runtime fails to make a proper conversion. Is this indeed our problem? Can anyone suggest a fix?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top