Doug Murphy
dw-murphy at cox.net
Mon Sep 10 18:24:12 CDT 2007
Hi Dan, The variables are dimensioned, I just didn't copy that far up the routine. ADO is not referenced or used anywhere in this app so I did not define they type of recordset. All other code using recordsets seems to run fine, except for this one line. Thanks for the thoughts. Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Monday, September 10, 2007 4:03 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Jet version sql error >From off the top of my head, I would experiment with: 1) dim rst = Recordset OR dim rst = DAO.Recordset 2) try different recordset types Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: Monday, September 10, 2007 5:11 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Jet version sql error Folks, The basic question is do different versions of Jet require a different sql syntax. Background. We have a product developed as an Access 2002 runtime that is packaged using the Sagekey scripts for Wise. I am testing the distributable on different machine configurations, e.g., different versions of Windows, with/without different versions of Office installed, etc. All was going well WindowsXP, Windows Vista, until I tested the app on a clean (no Office, fresh install of windows) Windows 98 machine. When I open the program to a screen that opens a recordset based on an sql statement I get an Error 3075. The offending line contains (fldCountry = 'United States'), this is what is in the error message. The code that throws the error is as follows: sSQL = "Select * From tblUserFormat Where fldCountry = '" & sCountrySettings & "'" Set db = CurrentDb Set rs = db.OpenRecordset(sSQL, dbOpenForwardOnly) When I get the error sCountrySettings is = 'Unites States', but I am pretty sure it would throw the error with any string value. As I said this runs well when our installation is run in Windows 2000 or later. The only difference between the newwer and earlier windows installation is the version of Jet that installer puts on the computer. The older one is Jet 4 SP 8 for windows 98, 16 bit I assume. The later versions use another version of Jet 4 SP 8. Any idea why we see the error on Windows 98 machines and not others? Doug -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com