Place File on Desktop using Packaging solution

[scotthutchings]

I have created a batch file to enable users to update their FE database when new ones become available. I have 2 questions:

1. I have set up the installation package using the Package Solution Wizard to include this batch file and it places it in the same folder as the FE software. Is there a way to either a. create a shortcut to this file on the desktop as part of the installation procedure? or b.) move the batch file to the desktop as part of the installation procedure? The problem with the manual procedure is that the user must first unhide hidden files and show critical system files before they can access the FE files. I have a customer that is leaving for Vietnam on Friday where he will be installing it on several user's computers over there (the BE is located in California). He is not very computer savy and it makes me nervous sending him with a written procedure to move the file.

2. How can I replace the FE database with an updated database from within the database itself? When an update becomes available, I post it on the server and then each person must close the FE, click on the Update batch file (which copies the updated file to their local machine) and then reopen the file. I would like to create an update command button within the FE database itself that would do the same thing. Here is what I have in my batch file:

@ECHO OFF 
xCOPY [URL="file://\\192.168.0.101\share\ims\GGIMS\GGIMS.accdr"]\\192.168.0.101\share\ims\GGIMS\GGIMS.accdr[/URL] "C:\Documents and Settings\%Username%\Local Settings\Application Data\IMS\GGIMS.accdr" /y
ECHO IMS has been successfully updated.

I don't know how I can accomplish this. Any help would be greatly appreciated!

Scott

 

[ghudson]

1) Search the forum for there are threads discussing how to create a shortcut. I believe that I have posted the solution in this forum somewhere.

2) I did this once before. I would have the front end check the back end for a version number. If it did not agree, the front end would close its self and open another database that was programmed to copy the new front end over the old front end file and then open the new front end then close the database that did the copying.