[AccessD] Access error

Jim Lawrence accessd at shaw.ca
Mon Jun 29 12:21:39 CDT 2009


Hi William:

I am not sure now whether the decompile is working correctly. I added the
decompile feature to my 'file-type...MDB' options many years ago and other
than update it occationally depending on which version of Access I have been
using. I have not really checked it over.

Is there any more switches than just 
'C:\Program Files\Microsoft Office\office(10 or 11 or 12)\access.exe
c:\project\my.mdb /decompile' ?

Jim   

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman
Sent: Monday, June 29, 2009 6:27 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access error

Jim

...never saw that problem but I note you said you had decompiled
...on the off chance that the decompile didn't actually run,
...I've found using the decompile switch to be very buggy
...it works ...but only if I do it by the numbers
...by itself, it runs but does nothing leaving only the illusion of a 
decompile

...my process is:

    Turn Off CompactOnClose
    Decompile
    Exit
    Open w/Shift
    Compact w/Shift
    Compile
    Compact

...that actually works reliably, where just running the decompile itself 
often does nothing real.

William

--------------------------------------------------
From: "Jim Lawrence" <accessd at shaw.ca>
Sent: Monday, June 29, 2009 8:16 AM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
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




More information about the AccessD mailing list