I have a .mde that detects when a new version of itself is available (by 
comparing a local global variable in the front end with a centrally stored 
number in the back end).  A batch file is run which copies the new version 
of the front end onto the local hard drive.  Immediately the batch file 
starts, access is shut down.

Sometimes the new version placed onto the local hard drive is corrupted.  
I think this might be because the file is copied over before access has 
fully shut down (the speed of shut down depending on PC power, number of 
applications open etc).  Is there any way of delaying the start of the 
batch file until access has shut down?

Thanks for any help on this matter

Matthew

Matthew,

There are several ways of completing the task you are trying to
accomplish.  

Why not write a short VB exe that runs in the Startup group, it can
check the local ersion and the server version then copy a new version
down locally if required.

Or alternatively do it in Access if you don't have VB.

The version can be stored in a table in the database or why define and
use a custom property which is more hidden from prying eyes if you feel
the need.

I have even seen arrangements where there is no version checking and
every time the user starts the client PC it copies down a front end from
the server - this can useful in situations where the front end can
'expand' due to repeated use of append and delete queries.

The options are endless.......

Regards

Paul 

-----Original Message-----
From: matthew.abbott@s... [mailto:matthew.abbott@s...] 
Sent: 18 March 2002 16:21
To: Access
Subject: [access] mde file corrupts whilst updating

I have a .mde that detects when a new version of itself is available (by

comparing a local global variable in the front end with a centrally
stored 
number in the back end).  A batch file is run which copies the new
version 
of the front end onto the local hard drive.  Immediately the batch file 
starts, access is shut down.

Sometimes the new version placed onto the local hard drive is corrupted.

I think this might be because the file is copied over before access has 
fully shut down (the speed of shut down depending on PC power, number of

applications open etc).  Is there any way of delaying the start of the 
batch file until access has shut down?

Thanks for any help on this matter

Matthew

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1CF39.16CE0310
Content-Type: text/plain

Matthew,
I found a utility in the NT resource kit to delay the execution of a line in
a bat file called sleep.exe. You can put something like 
Command prompt:\> sleep.exe 10
in your batch file and it will just pause execution for 10 seconds before
the next line.
I found that it works in most cases depending on how long the pause is set
but Paul's suggestion of a VB exe is a better solution.
HTH
Omar

-----Original Message-----
From: Paul McLaren [mailto:paulmcl@t...] 
Sent: 18 March 2002 19:30
To: Access
Subject: [access] RE: mde file corrupts whilst updating

Matthew,

There are several ways of completing the task you are trying to
accomplish.  

Why not write a short VB exe that runs in the Startup group, it can
check the local ersion and the server version then copy a new version
down locally if required.

Or alternatively do it in Access if you don't have VB.

The version can be stored in a table in the database or why define and
use a custom property which is more hidden from prying eyes if you feel
the need.

I have even seen arrangements where there is no version checking and
every time the user starts the client PC it copies down a front end from
the server - this can useful in situations where the front end can
'expand' due to repeated use of append and delete queries.

The options are endless.......

Regards

Paul 

-----Original Message-----
From: matthew.abbott@s... [mailto:matthew.abbott@s...] 
Sent: 18 March 2002 16:21
To: Access
Subject: [access] mde file corrupts whilst updating

I have a .mde that detects when a new version of itself is available (by

comparing a local global variable in the front end with a centrally
stored 
number in the back end).  A batch file is run which copies the new
version 
of the front end onto the local hard drive.  Immediately the batch file 
starts, access is shut down.

Sometimes the new version placed onto the local hard drive is corrupted.

I think this might be because the file is copied over before access has 
fully shut down (the speed of shut down depending on PC power, number of

applications open etc).  Is there any way of delaying the start of the 
batch file until access has shut down?

Thanks for any help on this matter

Matthew






  DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee.  Access to this
message by anyone else is unauthorised.  If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful.  Please immediately contact the sender if you have received this
message in error. Thank you.