Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2017
    Posts
    8

    Post How to overcome Access Runtime problems?

    I am having problems with the following issues, so if someone could put a solution, I would be very grateful:
    1. I develop internal access-app for my company in Access 2016 x86 as mdb database so I could have ULS (User level security).
    2. My colleagues use is to enter that in specific forms via Access Runtime 2016 x86, in which I have no problems, but with 2013 x86 and 2010 x86 some macros do not work.
    3. The company uses on all PC-a Office x86 (2016 / 2013 / 2010) CTR - Click-To-Run, except on mine on which I have Office 2016 Pro x86 (MSI).
    4. CTR and MSI installers, according to Microsoft, do not work together, and if I use Office 2016 x86 CTR, I can not use Access Runtime 2016 x86, but 2013 or 2010.


    5. I have one macro with EMailDatabaseObject, but it does not work with 2013 or 2010.

    Can someone please help me / point me out how to solve this issue?

    Thanks.

  2. #2
    NTC is offline VIP
    Windows 10 Access 2013
    Join Date
    Nov 2009
    Posts
    2,392
    One must develop in the lowest/oldest version. Thus if some users are at 2010 - the development must be done in 2010 to avoid the dilemma that you are in.

    One solution is to bring everyone up to the 2016 run time. As you note, if one has the 2016 full license already then one cannot install the runtime - but then one doesn't need to. It will work fully already and if you are concerned about users getting into the design view then you should release the .mde version which locks it.

    Having said that - your other option, given the design is done, it to isolate the offending macros - and rewrite them using VBA instead. I have done this in the past.

    Finally I feel compelled to advise that releasing a discontinued feature (User Level Security) and an old file format (mdb) in 2017 is very unwise. There are very valid reasons for the feature to be dropped by Microsoft and the file type to be upgraded to accdb. You should instead work with the current product as defined by Microsoft.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 2
    Last Post: 03-25-2015, 10:27 AM
  2. How to overcome a deadlock in Admin privilege
    By Babu1983 in forum Security
    Replies: 1
    Last Post: 09-02-2010, 12:09 PM
  3. Problems with Access 2007 runtime
    By Drisconsult in forum Access
    Replies: 5
    Last Post: 08-22-2010, 12:04 PM
  4. Access 2002 runtime problems
    By Drisconsult in forum Programming
    Replies: 2
    Last Post: 07-24-2010, 03:57 AM
  5. Problems with libraries in runtime mode
    By Fouti in forum Programming
    Replies: 1
    Last Post: 01-18-2010, 10:02 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums