Problems with UTILITY.MDA

keith_pyrasoft

bit by bit . . .
Local time
Today, 01:30
Joined
Jun 11, 2003
Messages
39
I recently overcame mde build problems that I had been encountering (separate post) by realising that the Access 97 db in question had inappropriate references in it (namely Microsoft DAO 2.5/3.5 Compatibility Library and UTILITY.MDA instead of Microsoft DAO 3.51 Object Library). This I rectified.

However, although I can now consistently build an mde file, and I have also been able to decompile the mdb, I have the following situation:

I can get a clean mde build, but compiling explicitly in the mdb now gives the error 'User-defined type not defined' in (typically) the statement Dim PassDevN As udtDevNames. The implication here being that user-defined types are no longer supported.

The following was then discovered:

Adding UTILITY.MDA as a reference permitted a clean explicit compile of all modules, but any attempt to build an mde failed with an Access error. Worse still, closing the mdb and re-opening it reintroduced the 'User-defined type not defined error'. Taking UTILITY.MDA out of the references and immediately putting it back in rectified the situation until, of course, the mdb was closed.

Building an mde without UTILITY.MDA in the references worked fine, and curiously, the functions concerned worked!

I am proceeding at the moment with UTILITY.MDA removed, and therefore without the easy ability of test-compiling my modules……

Any ideas on this one would be very appreciated. I do seem to give myself exotic problems!

thanks

Keith
 
As a further thought -

Does anyone out there know of a link between User-defined types and UTILITY.MDA?
 

Users who are viewing this thread

Back
Top Bottom