Re: MDE questions

>There is no "auto conversion" feature that will turn macros into VB,

Select a macro, then:

Tools, Macro, "Convert Macros to VBA"

The conversion is not very good, but it does convert macro's to VBA.

(david)

"George Nicholson" <JunkGeorgeN@xxxxxxx> wrote in message
news:unRcd$sGGHA.3056@xxxxxxxxxxxxxxxxxxxxxxx
>1 & 2) There is no "auto conversion" feature that will turn macros into VB,
>so learning VB is necessary if you want to "convert" macros.
> 3) ADE does not require mde files. You can package MDb files as well.
>
> FYI: not sure what you mean by "Stand alone runtime". If you mean a
> single-file executable, there is no such thing with Access apps. ADE
> allows you to distribute a royalty-free "runtime" version of the Access
> executable *along* with your app. Some verison of msAccess.exe is *always*
> required to run an .mdb or .mde file.
>
> And distributing an application intended to be used with the Access
> runtime requires some extra development work:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odc_ac2003_ta/html/odc_acdeployADE.asp
>
> Preparing Your Access 2003 Database for Deployment, Part 2
> Under "Using the Access Run-Time Components"
> See "Differences Between the Access Runtime and the Retail Versions of
> Access"
>
> The above doesn't even include the error handling you can't currently have
> in your app, since you are only using macros.
>
>
> As far as the error message you are getting goes, did you do a Compact &
> Repair on the file before trying to make it an mde?
>
> HTH,
> --
> George Nicholson
>
> Remove 'Junk' from return address.
>
>
> "traveler" <traveler@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:053523D7-C20F-48E9-B82F-444AD0A97BF6@xxxxxxxxxxxxxxxx
>> I've read through lots of postings and haven't seen the answer yet so I
>> thought I'd ask --
>> I have a reasonably large Access 2003 application (about 65 MB) that I
>> want
>> to convert into an MDE so that I can later convert to a run-time app.
>> The
>> problem is that 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).
>>
>> I don't have all that many tables but I do have a LOT of macros (I don't
>> know VB so I have done everything with macros) [sigh!]
>>
>> I assume that I have to convert all the macros to VB. My first question
>> is:
>> do I have to convert/compile all these macros one at a time?
>>
>> My second question is: once they are converted, can I still see them
>> like
>> macros or am I then forced to learn VB so I can modify them that way.
>>
>> My third question is: If I'm going to be creating a stand-alone run-time
>> version with the Access 2003 Developer Extensions, do I have to create
>> the
>> MDE first?
>>
>> TIA for any assistance I can get on this!
>>
>>
>
>


.

Relevant Pages

  • Re: MDE questions
    ... >> 3) ADE does not require mde files. ... >> Preparing Your Access 2003 Database for Deployment, ... since you are only using macros. ... My first question ...
    (microsoft.public.access.conversion)
  • Re: MDE questions
    ... ADE does not require mde files. ... You can package MDb files as well. ... Preparing Your Access 2003 Database for Deployment, ... since you are only using macros. ...
    (microsoft.public.access.conversion)
  • Re: Open and eidt macro in code
    ... That is what I wanted to do - give them access to the design view, ... If your users are smart enough to be able to edit macros, ... Of course this precludes MDE. ... create an interface for them to accomplish the higher-level ...
    (comp.databases.ms-access)
  • Re: Open Locked Database
    ... In theory you can't make changes to forms, reports or macros, but there are third party tools out there to allow you some changes; not sure if there are any free ones, but a google search should do it. ... I saved the best for last: there is absolutely no whay you can do anything with the code in an .mde, simply because no source code is stored in an .mde, just the compiled which is out of reach. ...
    (microsoft.public.access.macros)
  • Re: sp_addlinkedserver
    ... *.mde is a compiled Access which serves as a front-end app. ... contains forms, querries, reports, views, modules, macros, etc. ...
    (microsoft.public.sqlserver.programming)
Loading