Conversion 97 - 2002 basics - pointers...

[PCS99]

Hi, I don't want to dumb down the forum but grateful if anyone can point me towards a 'Dummies guide' for converting an existing working Access97 with ODBC Oracle Db to Access2000 or 2002.

Used the wizard and it just told me 'compile error' Cannot find project or library.

The autoexec.bat calls a module which is failing at the first line!!! where we set up variables and can't get past it.

Function CurrSystem()
On Error GoTo Err_CurrSystem
Dim dbsCurrent As Database *** debug stops here..
Dim qdfFunction As QueryDef
Dim rstFunction As Recordset

Doesn't like Dim dbsCurrent As Database and so doesn't link into the Db.

If I open a linked table and enter the password the ODBC link works fine and all Oracle tables are accessible and some forms work.

The conversion errors table is the most unhelpful file I have ever seen! It tells me there could be a DAO syntax error!!.

The help on Access2002 seems to support this syntax.

Regards,

Pete

 

[arebelli]

Probably the problem is connectet to the refernce to DAO 3.6 library (in the references libraries).

By default access 2000 an 2002 does not use this library.

Try to look for this library in the list of references and control if the relative box in checked.

Then "uncheck" the activex data object library (this library conflicts with dao).

 

[PaulF]

see article

http://support.microsoft.com/default.aspx?scid=kb;en-us;319400

however, your problem is that the DAO Library is not selected in your References, and the fact that you didn't explicitly declare the variables.

Dim dbsCurrent As DAO.Database
Dim qdfFunction As DAO.QueryDef
Dim rstFunction As DAO.Recordset

Some things to watch out for....

if you use error traping, 2k and XP use different error numbers than 97....

if you made a switchboard using the wizard, it won't work until you've made some corrections to it....

explicit declaring of DAO objects....


If you want to use DAO for coding more frequently than ADO, then after selecting it in the References, move it above the ADO Library so that ACCESS will default to DAO instead of ADO.

Probably many more, but that are the biggies that I can remember.


PaulF

 

[PCS99]

Folks,

Thanks for you replies and they have allowed me to progress or at least understand the mechanism of failure! I'll study the white paper and continue. The only problem I had when trying to alter the converted file was a security warning saying I didn't have exclusive access and it wouldn't save changes.

It is a secured mdb file with an mdw and I was the only person logged in and with admin rights so I'm sure that will make sense shortly as well!

Regards,

Pete