Deploy Updated Changes in Front End 1

[Lhuffst]

I have a system that the backend is on a server and the frontend is on the users local pc's. It is necessary to make code changes to the frontend. Is there an easy way to deploy these changes to the frontend instead of physically going to each pc?
Thanks
Lhuffst

 

[Ed2020]

Give the users a batch file to copy the master copy of the frontend from the server to their local drive and then launch the frontend.

If the users always run this to open the database then they will have a fresh copy of the frontend copied every time they use the database and will therefore always have the latest version.

Ed Metcalfe.

Please do not feed the trolls.....

 

[dhookom]

Tony Toews offers a free updater at

http://www.granite.ab.ca/access/autofe.htm.

I generally use Ed's method of just copying a new front-end to the users' PCs.

'===================
'
' File: runQDAT.vbs
'
' Date : 07/14/2005
'
' COMMENT: Create a subdirectory on the users' H: drive and copy
' the latest version of the QDAT_Query front end
'===================


   Dim fso  'to be used for file related code
   Dim f
   Dim wsh
   Set wsh=WScript.CreateObject("Wscript.Shell")
   Set fso = CreateObject("Scripting.FileSystemObject")
   If Not fso.FolderExists("H:\QDAT") Then
      Set f = fso.CreateFolder("H:\QDAT")
   End If
   'delete the old file if it exists
   If fso.FileExists("H:\QDAT\QDAT_Query.mdb") Then
      fso.DeleteFile("H:\QDAT\QDAT_Query.mdb")
   End If
   'copy the new version files to the user's H drive
   fso.CopyFile "N:\DEPTS\QA\QDAT\QDAT_Query.mdb", "H:\QDAT\"

   wsh.RUN "H:\QDAT\QDAT_Query.mdb",3
   WScript.Quit

Duane MS Access MVP
Now help me support United Cerebral Palsy

 

[Lhuffst]

Thanks everyone. That will do the trick!

 

[Lhuffst]

I copied the code from above but when I run it, I get error 424 - Need object on the following line of code
Set fso = CreateObject("Scripting.FileSystemObject")

I realize that I have to dim fso but wasn't sure what to dim it as. I really do not have much experience in this area and appreciate any and all help.
lhuffst

 

[jrbarnett]

This is VBScript - its an operating system scripting language supported on Windows 2000 and above.
One of its "features" is that there's no specific typing of variables, hence no "As datatype" after the Dim statements.

If you can't run that, go to the Microsoft website and download and install the scripting runtime.

http://www.microsoft.com/downloads/...43-7E4B-4622-86EB-95A22B832CAA&displaylang=en

If you're not running Windows 2000 or XP, let us know which OS you are running - most likely a batch file as Ed2020 suggests will suffice.

John

 

[akirekab]

I have been working on Access project in my XP 2020 pro setup. It was developed in Access 2003.I was pretty sure I could do this without issues. Now although the original developer can open and run the app in 2003 and in 2002 at his office, I can not open the exact same file without the "Mehtod or data member not found" coming up".

Do I have to make some sort of adjustment. He tells me there were indeed some changes in the behind the scene code for Combo boxes among other things.

Only difference I see in referece library is 2002 has 10.0 object lib, and 2003 has 11.0 object library.

If you know how to help me I would appreciate it.

 

[dhookom]

akirekab,
Start a new thread.

Duane MS Access MVP
Now help me support United Cerebral Palsy