We have run across this error a few times (including this morning). It
turned out to be a DLL/OCX version problem. In our case an applicatin was
built using a newer version of comdlg32.ocx, but was installed with an older
one. We simply recompiled the EXE with the older one, and the ewer one (when
it exists on the target machine) is backwards compatible.
Quote:
>I believe I have seen this question somewhere else, anyway:
>Have you had a look at Article ID: Q176438 from the KB?
>--
>VB-Joker
>MCSE
>Please post all replies to newsgroup!
>>What is this runtime error and where would I find any documentation for
>this
>>... I use DAO with VB5.0 and cannot determine why this happens on certain
>>workstations only and in only 2 of the 7 modules ?
>>Thanks for your help!
>>--
>>Anu
>>** remove 'nospam' from email to reply