I have a database back end that sits on our server and the front end sits on each users desktop. Whenever I update the front end I place the new copy into a folder on the server. When a user opens their desktop front end a piece of code checks if the date/time of the front end on the server is more recent that the one on their desktop. If true, their front end automatically opens a small database, (then closes their Front end), that uses FileCopy source, target to copy the more recent front end onto the users desktop. I do it this way because it obviously won't let me copy a new file onto the desktop if the database is still open.
My problem is that everything was running well until we upgraded to office XP. I in turn upgraded all the database files to access 2002. Now the database goes through the procedure of copying a new version but it doesn't actually do it. I've stepped through the code with no problems and it carries out the FileCopy action but when I check the new front end it's actually still the old one? I've converted the mdb's back to 2000 but the problem still remains! Has anyone every seen anything like this before?
My problem is that everything was running well until we upgraded to office XP. I in turn upgraded all the database files to access 2002. Now the database goes through the procedure of copying a new version but it doesn't actually do it. I've stepped through the code with no problems and it carries out the FileCopy action but when I check the new front end it's actually still the old one? I've converted the mdb's back to 2000 but the problem still remains! Has anyone every seen anything like this before?