VB6 Project is not compiling under Win2K only!!!

[tatochka]

I have a VB6 project created on Windows98 machine and worked just fine. Using VB Package and Deployment Wizard I created an installation program and strated testing it on Win2K. I installed it on Win2K with no problem,but when running the application got the following error "Myapplicname.exe has generated errors and will be closed by windows. You will need to restart the program." After spending some time with trying to figure out
what is wrong, I decided to install VB on the machine and compile the project on this machine. But the project is not compiling giving me the same error message (only vb.exe instead of my applic. name) and pointing
to the following peace of code:

Global gAssetdb As dao.Database
Global Budgetdetail As dao.Recordset
Global gAssetdbpath As String
Global gAccessVersion As String
Global sqlstmt As String
....

Set BudgetDset = gAssetdb.OpenRecordset(sqlstmt, dbOpenDynaset)
frmMonthly!Data1.DatabaseName = gAssetdbpath
frmMonthly!Data1.Connect = gAccessVersion
frmMonthly!Data1.RecordSource = sqlstmt

frmMonthly!grid3.Visible = True
.....
BudgetDset.Requery
Set frmMonthly!Data1.Recordset = BudgetDset

frmMonthly!Data1.UpdateControls
....

frmMonthly!grid3.Refresh
BudgetDset.MoveLast
....

BudgetDset.MoveFirst
Do While Not BudgetDset.EOF
....
BudgetDset.MoveNext
Loop

Error happens on BudgetDset.MoveNext. DAO 3.6 is used to connect to Access2000 database. There is no "missing" shown in reference list. Nothing is installed on the machine except Win2K and Excell2000. I downloaded all critical updates and service pack for Win2K and the ServicePack5 for Visual Studio. And another miracle: if I install Novel
Client on this machine, the error message disappears and application works just fine, I uninstall it and get the message and problem back. The users are not going to have Novel installed. PLEASE HELP ME!!! I am new in VB.

 

[Nagrom]

Is the Access database possibly on a remote machine that is only accessible using IPX/SPX?

 

[tatochka]

Everything is local .

 

[Nagrom]

Wait a sec... you say this is an Access database but you only have Excel2000 installed. Is that a typo or is that correct?

 

[tatochka]

That is right. Why would I need Access to be installed if I am using db through VB app. ? I didn't need it on other machines I tried.

Additional info if it helps. The error log is created in Dr Watson log file saying "Application exception occured: App: vb6.exe (pid=1108) Exception number: c0000005 (access violation)"

 

[Nagrom]

Are you sure you have the appropraite version of the driver to access (no pun intended) the database? DB drivers for older versions of Access may not be able to read the newer .mdb file.

 

[Nagrom]

Are you sure you have the appropriate version of the driver to access (no pun intended) the database? DB drivers for older versions of Access may not be able to read the newer .mdb file.

 

[tatochka]

I am not sure I understand this. How do I know what driver I have? Is it something I have to install additionally?

 

[chiph]

tatochka -

Check the versions of the Access driver in your ODBC administrator between the two machines. it is likely that the one with the problem has an older driver (or not one at all!)

Chip H.
Error on line 9: Object of type SIGNATURE expected

 

[tatochka]

Win98 machine has a Microsoft Access Driver version 4.00.5303.01 . Win2K machine has driver 4.00.6019.00 installed.

 

[NSpilker]

I have experienced a similar problem. Have you discovered an answer? Is it because of differing versions of the driver?

 

[tatochka]

Microsoft identified the problem to TrueDBGrid control (third party control) used in application. It made calls to some of windows dlls that I guess were changed in Win2K and Win2K security doesn't let you to replace any system dlls.
CompnentOne (the author of the control) could not fix it and the problem was solved when we upgrated to the next version of this control.