Interesting issue with the Front End Update Tool ( basFEUpdate )

MSAccessRookie

AWF VIP
Local time
Yesterday, 19:49
Joined
May 2, 2008
Messages
3,428
I have had great success using the Front End Update Tool ( basFEUpdate ) in one of my applications. When I installed it in a second application, it did not seem to work correctly.

The First Application works as advertised.
  • An update is recognized and the message is displayed
  • A replacement script ( UpdateDbFE.cmd ) is generated
  • The script ( UpdateDbFE.cmd ) is executed
  • The updated version replaces the existing one.
The Second Application does not work as advertised.
  • An update is recognized and the message is displayed
  • A replacement script ( UpdateDbFE.cmd ) is generated
  • The script ( UpdateDbFE.cmd ) does not appear to execute
  • The updated version does not replace the existing one.

The script that is generated for the second application does work when it is executed from Windows, but it does not appear to work within in the VBA Code. I was wondering if anyone had any ideas as to what I could look for to resolve the issues.

-- Rookie
 
How about putting the non-updated DB in the exactly same folder as the updateable DB , and see if that helps? If so, that would indicate that the script does not set the right directory, if relative paths are used. This could hinge on lack of " around paths with spaces, although I find that hard to believe if this is a tested tool.
 
Last edited:
Howzit

I have also had problems with this - and never got a resolution. My problem would pretty much did the same thing. It worked out a new version existed but could not run the cmd script that was generated. It did create the cmd script as an cmd.exe (or something to that effect) shortcut appeared on my desktop. I had to open this cmd button to complete the process.
 
How about putting the non-updated DB in the exactly same folder as the updateable DB , and see if that helps? If so, that would indicate that the script does not set the right directory, if relative paths are used. This could hinge on lack of " around paths with spaces, although I find that hard to believe if this is a tested tool.

Spike,

I am not sure this will work as the current VBA Code is written. More importantly, the .cmd script that is created is completely correct, and works if you run it. It just will not execute from the VBA Code.
 
Howzit

I have also had problems with this - and never got a resolution. My problem would pretty much did the same thing. It worked out a new version existed but could not run the cmd script that was generated. It did create the cmd script as an cmd.exe (or something to that effect) shortcut appeared on my desktop. I had to open this cmd button to complete the process.

Kiwiman,

Greetings from the USA. I posted here today in the hopes that I was not alone, and am sorry to hear that you have not been able to resolve the issue. I am hoping that we are not alone, and that someone else has found a solution.
 
It sort of depends on what the script contains. The default directory is not the same, so just because you can run it manually the result can depend, presumably, on from where. Also, if this has to do with permissions, placing the offending DB in the same dir as the OK-one might divulge that. And of course I am rambling, since I don't know that application.:D
 
It sort of depends on what the script contains. The default directory is not the same, so just because you can run it manually the result can depend, presumably, on from where. Also, if this has to do with permissions, placing the offending DB in the same dir as the OK-one might divulge that.

Although you may be correct, that was not what I was referrring to. The VBA Code (as written) expects that databases to have the same name, so thay cannot coexist in the same folder.

Your point about permissions is a valid one. I have both projects in separate folders within my personal sandbox and the new one still does not work, but I can copy the new project into the existing project folder and see if that makes a difference.

UPDATE: (11:00 AM) Moving the location that the new Application is stored in to the folder used by the previous application does not change the outcome. Thanks for the suggestion

UPDATE: (11:25 AM) Reversing the switch (Moving the new Application that the user runs to the previous testing directory and leaving the location that the new Application is stored in alone makes it work properly. Is it possible that the name or location of the user copy of the application is affecting this?
 
Last edited:
I would have thought that you cannot Rename, Move etc an Open Database.

Should it not be closed first.
 
From what I have been able to determine, the code does that. The code executes a shell command that first removes the existing database and then copies the new one into its place. The next line of code closes the existing database. Apparently this happens in a way that allows the current database to be closed before the command is executed.
 
Can you make the code run ANY script? Something totally innocuous?
 
Howzit

How's life over the pond?

I was using Bob Larson's front end updater at the time for this purpose. We had the application deployed on a Citrix environment and it would work ok most of the time, but randomly for some users it would fail. I could never replicate the problem on demand to really get to a root cause. I had only just started investigating environmental causes when I changed jobs - so unformately we had to live with the workaround by opening the cmd file that was created when it failed.
 
Maybe this could help.

Create a new Database that holds the information code etc for updating.

Create a Shortcut on everone's desktop that opens this file.

When opend, If Required, it copies the new Front End to the Users C:\Drive.

No need for a Backup as you would have many Backups in the course of your development.

It then opens the new Front End and closes itself.

I have done this before and can search for the code if required, but would not be able to do this until the weekend.
 
Maybe this could help.

Create a new Database that holds the information code etc for updating.

Create a Shortcut on everone's desktop that opens this file.

When opend, If Required, it copies the new Front End to the Users C:\Drive.

No need for a Backup as you would have many Backups in the course of your development.

It then opens the new Front End and closes itself.

I have done this before and can search for the code if required, but would not be able to do this until the weekend.

Interesting idea. I am willing to evaluate any options, but I was wondering why the one currently implemented was failing.
 

Users who are viewing this thread

Back
Top Bottom