Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MDE file problem 1

Status
Not open for further replies.

Bill4tektips

Technical User
Aug 5, 2005
175
GB
I currently have three databases. 1 for the base information tables, 1 as an .mdb and 1 as an .mde. Over the past week when I try to convert my .mdb to an .mde I get a message "Microsoft Office Access was unable to create an MDE database". When I click the "Help" button I get the following message "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."

The database has worked for about a year quite happily and I have another two identical databases (with different front ends to accomodate different priviledges, both these other databases convert OK.

Any ideas anyone as to how to overcome this problem?

 
Does the .mdb compiles properly ?
When in VBE menu Debug -> Compiles ...

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
When trying to compile I get the message "Sub or Function not defined" in
Private Sub Form_Load()
' Turn the MouseWheel Off
Dim blRet As Boolean
' Call our MouseHook function in the MouseHook dll.
' Please note the Optional GlobalHook BOOLEAN parameter
' Several developers asked for the MouseHook to be able to work with
' multiple instances of Access. In order to accomodate this request I
' have modified the function to allow the caller to
' specify a thread specific(this current instance of Access only) or
' a global(all applications) MouseWheel Hook.
' Only use the GlobalHook if you will be running multiple instances of Access!
blRet = MouseWheelOFF(False) ***THIS IS HIGHLIGHTED
End Sub
 
You probably have a missing reference:
menu Tools -> References ...

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Who wrote this code dealing with the mouse wheel ?
Ask him which DLL was required.

Another way is to comment out that code ...

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
mousewheel.dll is the file used. The guy that set this up has retired and I have been saddled with keeping it maintained.
 
So, you now know which DLL you have to register and reference.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top