Converting to Access 2003 - probs

[MariamS]

I have an access (*.mdb) that was originally used in the '97 version. Eventually it was "converted" to 2000. Still using the 2.5/3.0 compatibility library. A number of programmatic changes (per the compiler) had to be made, but eventually it worked.

After compacting and repairing, I converted to 2002-2003. Without changing the DAO to a later version, there are no compilation errors. If I run the database and try to perform certain actions on some of the forms I get some run-time errors (2450) - can't find the form...and program halts.

Please inform me as to what issues I may have, how to proceed. I have tried to change the DAO library to 3.6 and made programmatic changes but still ran into the same issues of not finding the form, etc.

Thanks so much for your time, I appreciate it.

 

[lamarw]

You should first try running the 'debug' on any code you have. I've experienced some code loss in the situation you describe. Running debug while in the code editor often times will reveal problems that must be fixed.

 

[MariamS]

I compiled without error. However, I am experiencing an issue with one of the forms where I get "...access has encountered a problem and needs to close..." With an option to repair my open database and restart.

 

[lameid]

The only thing I can think might isolate the problem is to try the following...

Try importing the Suspect form within Access 2000 to a new Access 2000 database. Covert the just a form database to the 2003 format. Import from that database the into the broken 2003.

Also make sure you have all your driver and office patches. Reinstalling Office 2003 and starting the conversion from 2000 may produce better results too.

 

[MariamS]

I went through the code and found that it is closing the program when/after executing the last line listed below:
"Set rstfoxpoap = dbsJet.OpenRecordset(FoxDbf)". The table is linked and I was successful in opening them and accessing them from another form within the same prgm.
Thanks,
Mariam


Dim dbsJet As Database
Dim rstfoxpoap As Recordset
Dim foxpath As String
Dim FoxDbf As String

Dim PURCHORD_PONO As Double
Dim Supplier_ID As Double

T4.Seek "=", Forms![Global Values]![txtPONO]
Supplier_ID = T4.supplierid
T5.Seek "=", Supplier_ID

foxpath = T3.JcPoApDir
FoxDbf = T3.JcPoApDbfName

T3.Close

Set dbsJet = OpenDatabase _
(foxpath, False, False, "Foxpro 2.6;")

Set rstfoxpoap = dbsJet.OpenRecordset(FoxDbf)

 

[lameid]

It looks like you backend database is Foxpro 2.6 and not Access (based on the code). I'd do a search for updated Foxpro drivers for Office 2003 functionality.

Happy hunting.