"Make Accde" fail...

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mshakeelattari
    New Member
    • Nov 2014
    • 103

    #1

    "Make Accde" fail...

    I have a database file in accdb format with a linked accdc backend data file containing more than 50 queries, more than 30 fomrs, about 30 reports, four macros and about 10 vba modules. The front-end file is about 42.8 mb. Now when I try to save it as "Make accde", it fails showing a message as unable to create accde file with a button 'show help' with following text:
    "This error is usually associated with compiling a large database into an MDE file.* Because of the method used to compile the database, a considerable number of TableID references are created for each table.* The Access database engine 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 Access 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."

    What is solution please?
  • PhilOfWalton
    Recognized Expert Top Contributor
    • Mar 2016
    • 1430

    #2
    Are you using any library databases?

    Phil

    Comment

    • zmbd
      Recognized Expert Moderator Expert
      • Mar 2012
      • 5501

      #3
      In this case, most likely there is an issue with your code.

      + MAKE A BACKUP COPY OF YOUR FRONT-END
      Cannot stress that enough!

      With your front-end:
      + Database tools \ Compact and Repair Database
      + See the following: Post#2-StepA

      Make sure that the Option Explicit is set, etc... repeat the debug/Compile step until it compiles without error(s).

      + One more compact and repair.

      > At this point if all is good, make a backup of this version of your front-end. You will want a non-accde version for further development. I highly recommend always making backups and never using the sole copy!

      Now attempt the make ACCDE with the "compiled" version.

      > similar issue in this thread Post#4
      Last edited by zmbd; Jun 12 '16, 01:49 PM.

      Comment

      • informerFR
        New Member
        • Jun 2016
        • 14

        #4
        Hi mshakeelattari

        Don't forget to compile your VBA code (go to VBA editor -> debugging -> compile) before creating an accde db.
        Last edited by zmbd; Jun 12 '16, 07:02 PM. Reason: [z{that was already given}]

        Comment

        • mshakeelattari
          New Member
          • Nov 2014
          • 103

          #5
          Hi informerFR, Thank you very much. Your suggestion worked...!
          Last edited by zmbd; Jun 18 '16, 05:14 AM. Reason: [z{please see post#3}]

          Comment

          • mshakeelattari
            New Member
            • Nov 2014
            • 103

            #6
            hi Phil, will you like to tell a bit about library databases? please

            Comment

            • PhilOfWalton
              Recognized Expert Top Contributor
              • Mar 2016
              • 1430

              #7
              Glad to see your problem is sorted.

              Briefly, you know with your in the References, you have a reference to say "Visual Basic for Applications", "Microsoft Access 14 Object Library", and, if you are using Excel in your program, "Microsoft Excel 14 Object Library", well in the same way you can have a reference to an AccDb or an AccDe. In my case "Utilities.AccD b".

              In my case, over the years, I have developed a "Utilities" database that I use with nearly all my other database.

              It contains only forms & Code, and deals with things common to most databases. So all the information for those forms comes from the main database.
              Included is a Treeview type menu system with forms to set up which users can use which forms, Company information forms, forms to deal with folders where the main database has various tables, routines to check backups are done on a regular basis, functions for extracting data from date information. That is only a small fraction of what it does, as the database is 4.7Mb so it's quite big.

              In a way it's a bit like normalisation. If I find I have the same routine or form occurring in a number of my main database, I tend to remove then from the main database and put them in the Utilities Database.

              Interestingly, the utilities database has a reference to a further database called "ShrinkerStretc her" from Peter's software. That makes a very good job of resizing forms in the main database, so as you shrink a form, the text boxes. combos, pictures, subforms, fonts all shrink in proportion.

              Phil

              Comment

              • zmbd
                Recognized Expert Moderator Expert
                • Mar 2012
                • 5501

                #8
                mshakeelattari,
                Best to start a new thread about "library" databases if you need more of an explanation than Phil has already provided.

                Also, please see your Bytes.com InBox
                -z

                Comment

                Working...