Hi all -
This is sort of Access related but mostly not...
In my current configuration, an end user clicks a batch file on their desktop that replaces a users front end on their C: Drive with a master front end on a network drive and then launch the application. (this allows for live updates and automatic upgrades)
Problem is, When the Batch file is done running and Access Opens, the batch file stays open in the background until the user manually closes it or the database is closed.
Any thoughts on how to code this differently or where my bug is happening? Its on a Windows 2000 system running Office 2000.
Heres the DOS Batch Code I'm using:
[red]
cd "S:\CCDBv3.0"
S:
del C:\CCDB\CCDB_v3.0\CCDB_v3.0.mdb
copy Front_End\CCDB_v3.0.MDB C:\CCDB\CCDB_v3.0 /Y
C:\CCDB\CCDB_v3.0\CCDB_v3.0.mdb
Exit
cls
[/red]
Thanks for any help you might be able to provide.
Andy
This is sort of Access related but mostly not...
In my current configuration, an end user clicks a batch file on their desktop that replaces a users front end on their C: Drive with a master front end on a network drive and then launch the application. (this allows for live updates and automatic upgrades)
Problem is, When the Batch file is done running and Access Opens, the batch file stays open in the background until the user manually closes it or the database is closed.
Any thoughts on how to code this differently or where my bug is happening? Its on a Windows 2000 system running Office 2000.
Heres the DOS Batch Code I'm using:
[red]
cd "S:\CCDBv3.0"
S:
del C:\CCDB\CCDB_v3.0\CCDB_v3.0.mdb
copy Front_End\CCDB_v3.0.MDB C:\CCDB\CCDB_v3.0 /Y
C:\CCDB\CCDB_v3.0\CCDB_v3.0.mdb
Exit
cls
[/red]
Thanks for any help you might be able to provide.
Andy