Results 1 to 10 of 10
  1. #1
    5 Star Lounger
    Join Date
    Jan 2001
    Location
    Ephrata, Washington, USA
    Posts
    683
    Thanks
    0
    Thanked 0 Times in 0 Posts

    MDE - Linked Tables (97 SR2)

    I must confess. I don't know the difference between creating an MDE and using the Split Table Manager. Do you do both? If so, which one is first? I am comfortable splitting the database and using linked table manager. But, what is the reason for Make MDE? Thanks for not laughing at me!

  2. #2
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: MDE - Linked Tables (97 SR2)

    First of all, an MDE has nothing to do with splitting the database. An MDE is essentially a compiled version of an MDB database (although, don't confuse this with an executable, like produced by VB). You can not modify the design for any objects in an MDE. This makes it useful because it hides your code, and prevents any users from doing anything too destructive. It also supposedly has better performance, but I'm not sure it is significant, so I wouldn't use it as a selling point. You would only make an MDE out of your frontend MDB.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: MDE - Linked Tables (97 SR2)

    In more advanced designs, you would also make MDEs out of library databases.
    Charlotte

  4. #4
    5 Star Lounger
    Join Date
    Jan 2001
    Location
    Ephrata, Washington, USA
    Posts
    683
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE - Linked Tables (97 SR2)

    Thanks. That helps a lot. One more question, if you are going to make an mde, then what is the point in spilitting the database? I thought that was to protect the data from the user. Does it make sense to do both?

    And, Charlotte... thanks. That is so waaay over my head that I'm not even going to ask!

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: MDE - Linked Tables (97 SR2)

    MDEs protect object design--forms, reports, code, etc. Your users can do all sorts of stuff, but they can't save design changes. <img src=/S/joy.gif border=0 alt=joy width=23 height=23> Since you can't make design changes to an MDE, and since you might want to share the database, you need the back end separate so that multiple front ends can link to it and so you can compact the data file periodically.
    Charlotte

  6. #6
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: MDE - Linked Tables (97 SR2)

    Expanding on Charlotte's response, when you create an MDE it "protects" or hides the design of forms, reports, macros and modules. However you can still change, add or delete tables and queries. On the other hand the idea of splitting a database puts the tables in one database (referred to as the back-end), which means the data is typically stored on a server in those tables. The front-end database has all the rest of the objects (queries, forms, report and code), contains links to the tables in the back-end, and is often put on the user's PC so that better performance is achieved when loading forms and reports. In addition as Charlotte noted, the front-end concept makes it easier to make design changes once the database is being used. Hope this helps clarify what each does.
    Wendell

  7. #7
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE - Linked Tables (97 SR2)

    We need to distribute databases to customers who have older versions of Access. We believed that MDE files would run on PCs regardless of wheather the user had Access or not. Can you tell me more about the differences in a VB executable and and MDE? We have done some development in Access XP (2002 format) and need to distribute it to a customer who has an older version of Access (97). I made an MDE file thinking that it would run on the user's pc and it did not. He got the "...unrecognized format..." message. I then thought about making a Visual Basic Executable that connects to the Access db that the user could run. Before I begin the process of making the user interface in Visual Basic, I want to find out if this is a workable solution. Also, we tried to convert the XP back to Access97 and have some debugging issues related to Microsoft Graph.

    Any thoughts?
    Thanks,
    aap2

  8. #8
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: MDE - Linked Tables (97 SR2)

    An MDE is not at all equivalent to a VB executable. You have to distribute the Access runtime along with the MDB or MDE for a user without Access (or without the correct version of Access) to run the application. In order to distribute the runtime, you need the license that comes with the Developer edition of Office.
    Charlotte

  9. #9
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: MDE - Linked Tables (97 SR2)

    You wrote:
    >>We need to distribute databases to customers who have older versions of Access. We believed that MDE files would run on PCs regardless of wheather the user had Access or not. Can you tell me more about the differences in a VB executable and and MDE? <<

    You belief is mistaken. An MDE database is a compiled version of an MDB database, such that it no one can change the design of any objects. However it is NOT executable; the user must have a version of Access and furthermore, it must be the same version as the MDE!

    You can legally distribute a royalty-free runtime version of Access, provided you have the Office Developer Edition. However, you need to be REALLY careful with installing the runtime if user already has another version of Access.

    If you aren't really sure of the situation in which it will be installed (and you don't want to support multiple versions of your database (one for each Access version), then I'd strongly recommend looking at VB instead of Access.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  10. #10
    2 Star Lounger
    Join Date
    Jun 2001
    Location
    Virginia, USA
    Posts
    127
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE - Linked Tables (97 SR2)

    Thanks Charlotte and Mark. I have read posts in this forum related to distributing run time versions to users with other versions of Access on their pc. I have come to find out that of the copies that we need to distribute, some have Access 97 and one Access 2000. I am investigating known issues.
    Thanks for your help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •