"Microsoft Access can't find the VBA dll vba332"

Yes, Kees, I do.
I just didn't use the same search terms that you did, but the full error message, which did give me some interesting suggestions.
Thanks for the message. I'll look into the suggestions on that forum.

The credible answer you described has 2 problems:

1. There was not registry key of that name in the registry. And the author did not say that he wants the user to create it.

2. I'm not sure if I should be playing around with the registry unless I know the person advising me definitely knows what he is doing. Do you know the person who wrote that advice? Can he point to a Microsoft knowledge base article stating that that is a valid, approved fix?

Also, I tried the regsvr solution and that didn't work either.
Thanks.

He installed Windows 2000 first, then Office 97, all the SP2 and patches, then upgraded the machine to XP Pro.

His machine fell victum to a failed hard disk and he tried to not go through that again and found that he couldn't get all of Office 97 running again in spite of answers from Google.

After repeating the above, later the spell checker failed. Then something else and the last I heard he was limping along by telling XP that it was a '95 application.

After watching so many struggle, I think its dead, Jim.

Bob

It's past midnight here now.

See you,


Kees

There's one last option you didn't mention --
if it's neither business nor student.
In which case, it's ......$400!

Unfortunately, this is the option that applies to me.

Even a laptop. But everything depends on your needs, of course.

By the way: Access 2003 = $ 194.99 at http://www.amazon.com/exec/obidos/ASIN/B0000AZJV4/102-6556564-4262560
That's half of what you mention.
And you might be able to find Office 2000 (or Access 2000 only) second hand at eBay for far less. That's recent enough for XP and very well compatible with Access 97. No guarantees for upcoming Vista.

Good luck,


Kees

You wrote:
A second hand Windows 98 PC is much cheaper.

Such as, the one I just upgraded from (and am still in possession of).

The Ebay suggestion was good. I should have thought of it myself. Thanks for your suggestions.

Looks like Microsoft is up to its old tricks.
Imagine creating an OS that doesn't support an Office Suite that your own company introduced only 4 years earlier (2001 - 1997 = 4)!
Only Microsoft could get away with it!
Perhaps its time to use OpenOffice.

Kees wrote:

"Access 2003 = $ 194.99 at http://www.amazon.com/exec/obidos/ASIN/B0000AZJV4/102-6556564-4262560
That's half of what you mention. "

I mentioned $400 as the retail price of the FULL Office suite, not just Access. So spending half of that for just Access (i.e., for one-fifth of the full suite)is actually rather expensive.

Kees wrote:
"On my Windows 95 machine, I had Office 97 (including Access) installed, and 5 references to this dll:
- in HCR\Typelib
- in HLMS\Classes\Typelid
- in HKLM\Software\Microsoft\Shared Tools\MRT3ENU\Clients
- in HKLM\Software\Microsoft\Shared Tools\VBA322.DLL
- in HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs

On my XP-machine with Office 2000 installed (including Access) there's no reference at all.

I'm rather sure the standard install of Office did this. And if doesn't do it in XP it seems rather hopeless to mee."


I'm not quite sure I grasp your logic here Kees.
Why should it be surprising that Office 2000 doesn't reference the same .dll's that Office 97 does? They're 2 different products, aren't they?
What does this fact have to do with my problem, which is installing the same product, i.e., Office 97, on a different PC?
If it were OFFICE 97 and not Office 2000 that you have installed on your XP machine, THEN it might be noteworthy if the XP machine didn't reference the same .dll's.
Or perhaps I misunderstood your point. If so, please explain.

- It's Office 97 specific.
- If none of those entries are in the registry, it seems impossible to repair manually.
- If just the last one is missing, it's worth a try.

That's all. Sorry for the misunderstanding.

Kees

Kees wrote:

"If all of these are missing, the only thing I should try is a repair install from the Office CD. It might fix it"

Doesn't the repair option simply rewrite any corrupted files on the hard drive? If so, I don't see how that would work since the same problem occurred even after I reinstalled Office 97 a second time. Did I get two corrupt installs in a row?

It's been discussed at length in many forums.

If costs are an issue, maybe it's time to move to Open Office 2.0 or better. It now has a database.

Top notch and the price is right.

Bob

If install doesn't do it, it's unlikely repair will. But if it's the only (even remote) possibility, and totally harmless, why not try? The alternatives (buying a newer version or going OpenOffice) aren't very attractive in the short run either. Although I fear they might be necessary.

Kees

Why is OpenOffice not a very good alternative?

OpenOffice is a good (albeit slower, but no problem for current machines) alternative, at least for Word, Excel and Powerpoint.

But the database module is new, in version Open Office 2.0. And I'm afraid it's rather incompatible with MS Access, that relies heavily on VBA for any serious project).
Someday, I'll download OpenOffice and have a look at it. If, in the meantime, you would post your experiences here, I would be most interested.

Kees

What programming language does Base use for creating database applications?

Faith,

I really don't know. Never seen the product. It's free to download, so if you're interested: have a look yourself.

Kees

Thanks Proffitt.

I WAS actually aware of the existence of the Wikipedia web site (and a few dozen others that deal with the subject).
When I asked Kees about the programming language, it was more of an opened-ended question, an invitation for him to provide his own thoughts and opinions about using the product. Since he has not used it, I suppose I will be the one who ends up doing that.

The cost to our office to keep with Microsoft's Office was quite the number to behold. So after we found most using Word for memo's we embarked on a bold plan.

Install Open Office as our standard and the user would have to justify why they needed MS Office. Most of the first justifications were that they needed to exchange documents with other MS Office users. Since Open Office does that already we could show them that we could open and save .doc and .xls files.

We moved away from Access years ago due to data reliability issues and that everytime MS issued a new version, the database would become inoperable with the old version of Access. Today I'm in the thick of using MySQL solutions that I've written via Visual Basic. It's been great.

Open Office, MySQL and your coding skills can make for a powerful cost deterrent.

Bob

Bravo Proffit. I wish more companies had the self-confidence to do this. There's plenty of software out there that beats what Microsoft makes.