• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Update the Access Runtime version of program

We have an access program that had an update made to some of the reports.  It works fine for everyone who has Access loaded on their workstation.  However, we have some people who use the Runtime Library.  They are not seeing the updated reports.  Using the runtime libraries was set up by someone who is no longer with the company.  Is there something that needs to be done so that those using the runtime libraries see the updated program? Note - the database is centralized and users have shortcuts on their desktop to use the centralize copy.
0
kshumway
Asked:
kshumway
  • 6
  • 6
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
They can't run the app at all or just don't see the new reports?  If the latter, check that the shortcuts are pointing to the DB that was modified.

JimD.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:

 and BTW that's not the best setup; the app should be "split" into a front end / back end and each user should have their own copy of the front end (which has everything but the shared tables).

JimD.
0
 
kshumwayAuthor Commented:
They don't see the report.  The shortcut is correct.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<They don't see the report.  The shortcut is correct. >>

  That's really not possible. The "runtime" of Access is nothing more then the full version with the design features disabled.  It's not going to see a DB any differently then the full version.   In fact you can start a full version in runtime mode by using the /runtime switch.

  If the shortcuts are using a mapped drive letter, I would verify that they are mapped correctly.  Also check that the modified DB is where you think it is and is named correctly.

 One simple thing you can do is:

1. From a station with the full version, use explorer to navigate to the directory where the db is.
2. Double click it and make sure you can see the reports.
3. Close Access and from the explorer window, rename the DB by added a prefix. i.e.

  myApp.MDB

  is now

  new_myApp.MDB

4. Now try one of the other stations using the shortcut.  If your pointing to the correct DB, you should get an error.  If it starts up, then your pointing a a different DB some how.

5. Don't forget to go back and rename the DB to what it was.

JimD.

 
0
 
kshumwayAuthor Commented:
When users using the runtime libraries enter data, it is in the database.  I can pull it up and see what they entered.  But when they print the report, it's a previous version of the report.    
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<When users using the runtime libraries enter data, it is in the database.  I can pull it up and see what they entered.  But when they print the report, it's a previous version of the report.     >>

  That would be possible if the application is "split" into a front end, which has everything but the tables, and a backend, which is a DB with only the tables.  The front end would have links to the back end and each user may have their own copy of the FE or not (it's better if they do).

  My guess from what your seeing is that it is split.

JimD.
0
 
kshumwayAuthor Commented:
No the program is not split - It's a very small access program that I created, not knowing that anyone using just the runtime libraries would be using it.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:

 Did you try the renaming procedure I gave above?

 In 18 years of answering Access questions, I have never seen nor heard of a runtime not seeing the same objects as the fuill version when looking at the same DB.   Even if there was some database corruption, both would see the same thing.

  As I mentioned, the "runtime" is nothing more then the full version with design features disabled.  It's the exact same EXE.  Only difference is some registry entries.

  There is no way that I know of that you can have the situation you describe.

JimD.
0
 
kshumwayAuthor Commented:
I'll try to connect to the workstations again and get some screen shots.  Perhaps I'm not seeing what I think I am.  I am working from home today, so will have to wait until tomorrow.  Thank you for your input!
0
 
kshumwayAuthor Commented:
OK I need to eat humble pie.  I found an error in my program that was causing the issue.  It had nothing to do with the fact that the user having the problem was using the Access Runtime libraries.  JimD was absolutely correct in his statements!  Sorry for the confusion and thank you for your support!
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<OK I need to eat humble pie.  I found an error in my program that was causing the issue.  It had nothing to do with the fact that the user having the problem was using the Access Runtime libraries.  JimD was absolutely correct in his statements!  Sorry for the confusion and thank you for your support! >>

  Not a problem.  Believe me when I say "been there, done that" LOL.

JimD.
0
 
kshumwayAuthor Commented:
Thanks for understanding!  Have a great day!
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now