[AccessD] Access error

Max Wanadoo max.wanadoo at gmail.com
Mon Jun 29 12:21:40 CDT 2009


Not advertising here, but if you export the whole lot to text files via
EatBloat (don’t know If John/Dan have re-written it yet) and then import it
into a new mdb you will drop any embedded control characters that may be
causing the problem.

Max



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: 29 June 2009 18:12
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access error

Hi Max:

No reference, nothing outside the usual other than a standard set of API
calls.

The MDB was working fine for a while and now it has decided to misbehave.
There must be something that has triggered its change of attitude. 

Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Monday, June 29, 2009 5:42 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access error

Off the top of my head Jim,

If you have a lot of References does this count against the overall count ?

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: 29 June 2009 13:17
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Access error

Hi All:

I have just run across an error in MS Access 2003 I have never seen before.

The Access is the proper format... 2003, a new DB was created and all the
objects were moved from another MDB... giving the same error, the code
modules compiles with no errors, the number of objects in the MDB is
relatively small and the MDB has been decompiled.

The error is as follows:

<error message>
Microsoft Office Access was unable to create an MDE database

This error is usually associated with compiling a large database into an MDE
file.  Due to the method used to compile the database, a considerable number
of TableID references are created for each table.  The Microsoft Jet
database engine version 4.0 can only create a maximum of 2048 open TableIDs
at one time.  Exporting a database as an MDE potentially can exceed this
limit if the database has a large number of objects (table, macro, form,
report, etc).
There is no accurate method to estimate the number of TableIDs the Jet
database engine uses during the process of compiling a database as an MDE. 
However, each VBA module and each form uses one TableID, as a result, if the
database has 500 forms, and each form's HasModule property is set to Yes, as
many as 1,000 TableIDs are used.

More information about this error message online.
</error message>

The error is as far as I can see is irrelevant. I will now be going through
object by object removing or adding and compiling until the error either
stops or starts.

If anyone has seen this type of error before and has been able to resolve or
better yet find out why, I would be very appreciative.

Jim


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list