Results 1 to 12 of 12
  1. #1
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    MDE files and Modules (Access 2000)

    I have made an mde file for the front end. I have modules which are used, but now they do not work. Do those modules need to be somewhere specific for an mde file to reference them?

    Thanks

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: MDE files and Modules (Access 2000)

    >> but now they do not work

    That is rather vague, don't you agree? What doesn't work? What is the error message that you get? Where does the error occur, and when?

    I assume the modules are present in the .mdb database from which you created the .mde? That should be sufficient. There is one very important prerequisite: since there is no code to be viewed in an .mde database, you must have explicit error handling throughout the code. Unhandled errors are very unpleasant to the user.

  3. #3
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE files and Modules (Access 2000)

    Anything that reference the modules do not work for users. What is wierd is that on my laptop, the code does work, unless I relocate the source mdb file (like change the folder). Currently I am trying to get a single user inside the company to use the mde file.

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: MDE files and Modules (Access 2000)

    1. Where are/were the source modules? In the .mdb used to create the .mde from, or in the backend, or in a library database?

    2. What are the references set in the .mdb used to create the .mde? Check this in Tools | References... in the Visual Basic editor in the .mdb.

  5. #5
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE files and Modules (Access 2000)

    The modules are in the .mdb file. The references are
    Visual Basic for Appllication
    Microsoft Acces 9.0 Object Library
    OLE automation
    Microsoft DAO 3.6 Object library
    Micrsoft Outlook 9.0 object library
    Micrsoft Word 9.0 object library

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: MDE files and Modules (Access 2000)

    Nothing remarkable there. You wrote that the .mde works on your laptop unless you move the original .mdb. Is there any explicit mention of the .mdb in the code?

  7. #7
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE files and Modules (Access 2000)

    Nope none. When you make an mde file, does the modules stay within the mde file, or do you need to place them somewhere?

  8. #8
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE files and Modules (Access 2000)

    I did change the paths of the location of the backend database. I will recheck them all tommorow on site. I could have something wrong there. Also, are there any other benefits to using an mde file?

    Thanks

  9. #9
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: MDE files and Modules (Access 2000)

    When you create an .mde, the code in the modules is 'compiled'; this compiled code remains in the .mde, while the source code is deleted. There is no need to do anything about this yourself...

  10. #10
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: MDE files and Modules (Access 2000)

    >>I did change the paths of the location of the backend database

    If the back end is not in the location where the front end expects it, most of your front end will not work, whether it is an .mdb or .mde.

    Benefits of an .mde?
    - the user can't change the design of forms and reports by accident or on purpose.
    - the details of the design of the forms and reports are protected.
    - an .mde is smaller than the corresponding .mdb since it doesn't store the source code.

  11. #11
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE files and Modules (Access 2000)

    Yeah I have noticed that. I am in the process of changing direct path references now [img]/forums/images/smilies/sad.gif[/img]

    Thanks for inout about .mde files

  12. #12
    3 Star Lounger
    Join Date
    Apr 2003
    Location
    Calgary, Alberta
    Posts
    327
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MDE files and Modules (Access 2000)

    I also noticed the scrollwheel workaround, the mousehook function (the one with the dll file) no longer works either. That code for the mousehook is also in a module as well.

    Ideas

Posting Permissions

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