This is similar to how we used to do it when we used floppy disks and kermit for file transfers ! It is an option I will look at if we cannot resolve this issue but the method we use doesn't seem particularly complicated and I'd like to avoid a rewrite if possible. We had to build in quite a lot of additional checks when copying files to ensure that correct files used etc and there are also some security concerns about keeping the information on the laptops as they tend to be left on the mobile units overnight. The main drivers for this are :
1. It should be easy to use (non technical users) 2. Reliable/recoverable etc Having the information used directly from the disk makes it easy as they just plug it in and it's ready to go. Its a good system (when it works) ! I tend to think this may be more of a windows/hardware driver issue than anything else but I'd like to get the software as robust as possible before going down this route. Mike "kevin furze" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Mike > > what about changing it slightly, > create Cache.dat on the removable disk as you currently do, > create a batch file on the laptop which copies the info FROM the > removable TO the laptop. then run Cache fromt he laptop pointing to the > laptop. > > you coulld do a BACKUP (allbeit full backup) onto the removable disk to > send it back to the master system > > the alternative is to have a restore type process that reads from the > removable to the laptop prio to usage. you could always call the > programme as part of the startup and validate if its been done once > today. > > it may not be the perfect solution, but on the basis you ahve problems > with corruption, then this may be a solution > > kevin >
