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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Errors when converting to 97 from 2000 1

Status
Not open for further replies.

dawnd3

Instructor
Jul 1, 2001
1,153
US
Hi All, this may be one of those things that everyone knows but me :) but I thought if there was a chance I could help even 1 person it was worth posting. I frequently have clients with Office 97 and I build their databases in 2000 and then convert when I am ready to deliver. I usually get a bunch of weird errors, some with the code which is understandable, but other errors regarding events that aren't related to the particular code. I finally discovered that creating a new database in 97 and importing all of the objects, fixes almost all of the problems. Easy, quick and no more headaches. Dawn
 
Do your clients get the errors "Expression is too complex to be evaluated" when they try to do simple things like select drop downs?

Are you using Sourcesafe as a source control provider?

 
Hi Lachie, I did get that error at one point, but the one I kept getting the last time around was "The expression On Current you entered as the event property setting produced the following error:.." and then a couple of comments about it being unable to evaluate the event procedure. This also happened for the After Update event I had on the combo box. As far as sourcesafe, no I have never used a source control provider. Is this something I should be doing? I have thought about it, but I don't know how or why yet. Thanks, Dawn
 
Hi, dawnd3!
Mostly errors what proceeded after I converted DB 2000 to 97 relevant to differences of libraries versions which are used in Access 2000 and Access 97 such:
Access 2000:
Microsoft DAO 3.6 Object Library (dao360.dll)
Microsoft Windows Common Controls 6.0 (SP4) (MSCOMCTL.OCX)

accordingly
Access 97:
Microsoft DAO 3.51 Object Library (dao350.dll)
Microsoft Common Dialog Controls 6.0(???) (comdlg32.ocx)
Microsoft Windows Common Controls 5.0 (SP3) (comctl32.ocx)


After I changed references and ActiveX objects on forms to previous version all worked OK.

I don't know either recognize Access 97 ADO library or not because I never use ADO but I use DAO.

Aivars
 
Aivars, that is probably why everything is fine when I import everything to a new 97 database. Thanks for the information, I have been wondering what library references should be in each one. Do you have a list of what all should be checked for basic database developement in each version? Or what is helpful to have referenced? Thanks. Dawn
 
Hi!
Exclusive of VBA default references I always create reference to DAO and place it in priority position 4 (after OLE Automation). References to ActiveX objects libraries Access create itself automaticaly after creating object on form. My experience show that errors often occur if reference to DAO is placed after some other refrences.

Aivars
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top