VB4 app, Jet 3.0

I've got an old VB4 app I want to look at to convert/re-write into something maintainable.

I have the source, but of course, nothing to compile it with, and VS2010 doesn't 开发者_如何学Golike the vbp and won't open it.

Although it installs, it won't run - failing with an out of memory error. I want to try an updated version of Jet 3.0, but I can't seem to get the files referenced in this link http://support.microsoft.com/kb/q151186/

So a few questions:

1) Where is the latest version of Jet 3.0?

2) Is running the app in VB4/5/6 the only viable option to be able to view the forms, designers, etc to convert the app?

1) If at all possible move to Jet 4.0/DAO 3.6 as they have been included in every version of Windows since Windows 2000. It's not worth your while trying to use an older version of Jet with all the install problems you will likely encounter. You might have a few syntax changes to make but I doubt they will be that severe.

2) I have no idea about how good or bad the upgrade path is from VB3 to newer versions of VB. If you don't get an answer here the real long time VB Classic (not VB.NET) experts hang out in http://groups.google.com/group/microsoft.public.vb.general.discussion/topics?hl=en That said the VB6 IDE works well in Windows 7 once you know about one particular install trick which requires creating a 0 byte msjava.dll file in the Windows directory.

1) Where is the latest version of Jet 3.0?

2) Is running the app in VB4/5/6 the only viable option to be able to view the forms, designers, etc to convert the app?

1 - I'd try to dig up an old copy of Access (or Office)

2 - Actually I doubt it'll even work in vb6 (and vb5 might be an adventure), the project upgrade paths weren't very smooth back then, but yes, you're pretty much stuck. As far as I know there was never anything else that would emulate those designers.

If you can find a version of VB4, or Access 95, then this would come with JET3.

2) Realistically you would need VB4 to have the best chance of opening this. Try to find someone who has some old MSDN disk sets.

You might try a later version. The jump from VB4 to 6 might be too much. I imagine it would open but perhaps not run in VB5 as I presume Microsoft looked at people upgrading projects from the immediately prior version.