Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / March 2008

Tip: Looking for answers? Try searching our database.

convert to mde with link table

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
May-G - 05 Mar 2008 20:02 GMT
Is possible to convert mdb to mde when you have link tables with the
database?  I try to convert the database to mde and received the following
message: "Microsoft Office Access was unable to create an MDE database".  I
only have 5 link tables, 3 queries, 6 forms and 2 reports.  I don't think
this is large database.  Thanks in advance.
Albert D. Kallal - 05 Mar 2008 20:08 GMT
Take your original mdb, and try to compile the code....

(just go ctrl-g, and then while looking at code go debug-compile).

Note that as a general rule, my fingers after editing code will go alt-d,
<enter key>

and then a ctrl-s

The above keys happens so often, and so fast that I can't even remember
doing it anymore. The trick here is to always compile your code. If you
don't compile code, then often inteli-sense will stop working. Only until
you fix all errors, does it come back.

Worse, if you edit some code, and close the code window, then it will
re-open when you return to the code window (ms-access still thinks you need
to work on that code since you did not compile it). So, not compiling your
code means all kinds of code windows open up when you return next time. And,
not compiling means that inti-sense often breaks, again, it can't work when
you got errors. And, last, but not least, with errors in your code, you
can't make a mde..

So, try compiling your code to find the error(s), and fix them (this is why
a mde is such a good idea, as you don't want distribute code with syntax
errors in it).

Once your code compiles...then you should have no problem making a mde...

Signature

Albert D. Kallal    (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

May-G - 05 Mar 2008 20:28 GMT
will try.  Thanks for the great tips.

> Take your original mdb, and try to compile the code....
>
[quoted text clipped - 23 lines]
>
> Once your code compiles...then you should have no problem making a mde...
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.