vb conversion problem

[Rev. Michael L. Burns]

I am attempting to convert and update a database to VB6 that was originally wriiten in VB4. As far as I can tell, all went ok and the program upgraded all ocx's and so on.

The program works fine from with the VB developement environment. However, when I compile it into an exe, although I get no errors during the compile, I never get beyond the splash scrren when running the exe. I get a message box with the following errro:

"An Error Occured in the System 3024"

Also, when you click ok on the message box the splash never unloads and I have to manually kill it. Agin, it all works fine in from with the VB6 IDE.

Any ideas?

Thanks,
Rev. Michael L. Burns
[email protected]

Error 3024 is a "File Not Found" error. Try putting

ChDir app.path

before you try to open the database the first time.

[Rev. Michael L. Burns]

Royce,

Thanks for you prompt reply. I suspected as much. However, the AppPath seems ok. All the MDB files are in the directory I use for the developement source code and the compiled program is in the same directory as well.

Any ideas why the files would be found when exicuted from within the IDE but not once compiled when everything is being run from the same directory?

Thanks,
Rev. Michael L. Burns
[email protected]

Well, I'm not sure what the problem is then...everytime I have a problem with a compiled version it's a path issue.

Just for kicks, make sure that you don't have more than one copy of the following files on your machine:

OLEAUT32.DLL
COMCAT.DLL
OLEPRO32.DLL
ASYCFILT.DLL
STDOLE2.TLB

You may be accidentally using a older version of one.

Otherwise, I would start adding message boxes into my splash screen (it's a rather heavy-handed but effective method of debugging ) Just do

' Some splash loading code
msgbox "1" 
' more splash loading code
msgbox "2"
'and so on

You can find what block is causing the error, and possibly trace it to one control. You'll probably find the problem there since the frmSplash.form_unload apparently never occurs.

One last suggestion: make sure you're opening the databases with Jet or ODBC (which you probably are, but I'm not positive about what controls VB replaces when upgrading forms.) Jet is fully backwards-compatible, and I would think this would fail during development also...

Anyway, that's where I'd start, hope it helps.

John

[Rev. Michael L. Burns]

John,

Thanks again for your prompt reply. I'll give it a try as soon as I can get back to it. Another thought that has crossed my mind is that it may be a licensing problem.

The code was given to be by another programmer to try to update and enhance. It uses a number of Classes and Modules from Paul D. Sheriff's PDSA Toolset. The PDSA Toolset is a generic application builder and set of templates for building Client/Server applications using VB 4.0.

I've seen other source before that ran in the IDE fine but would not run the compiled version because a license was missing. I don't know if that's the case here or not but if so, I'm down for the count. Although I'd love to upgrade, the current version of His PDSA Toolkit is $2,000. As a small church pastor who only wants to customize a few programs for use in my church, this is out of my league. I hope this isn't the problem.

Thanks again,
Rev. Michael L. Burns