Charlotte Foust
cfoust at infostatsystems.com
Tue Jun 19 10:57:23 CDT 2007
If the front end or back end drives are set to cache now write later, changes made on one front end might not show up in the back end immediately or be cascaded to other front ends in a timely fashion. Depending on how it was set up, it might delay the write until the initial FE app closed. Not what you want to happen. I would imagine that using a RAM Disk on any of the FE machines could also cause problems like that. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Friday, June 15, 2007 6:38 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Folder 'Caching' Hi Jim, I should have said that my system is a FE/BE Access 2003 system. Clients automatically pull updated FE files. Even when they do this, the new FE on the Client will think that it's supposed to link to the previous BE file. If the tables in the previous BE tables were changed, my system has crashed because the new FE is trying to connect to the previous BE, which no longer exists. It only does this once - the next time someone logs in after an update, everything runs smoothly. VF! (Very Frustrating) Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Friday, June 15, 2007 8:12 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Folder 'Caching' Hi Dan: I have only heard of the caching issue when relating to internet AJAX applications. IE caches everything and if a data request appears to be the same or very similar, it is just acquired from the cache. The solution to the problem is to prefix the date-time to each new piece of data. Not sure whether this relates to you as I am not sure how far caching use extends in the new programs. Jim -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Friday, June 15, 2007 3:57 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Folder 'Caching' Hello to all! I have a customer who, about a year ago placed my system under a networked folder they call Secured. It took me a year, but I finally was able to see a pattern of errors where updates to my system were not 'seen' by the first person who opened my system after an update, but they were seen by the second person and subsequent people who opened it. This has occurred where I made on change on Saturday morning and the problem occurred on Monday morning. Today we also experienced an email automatically sent to a Supplier that had the wrong due date on it! But when we looked into the back end later, the date was correct. Last week I attended a meeting with some IT folks at this company, and one of them said that he believed the folder was caching changes, but he didn't know the details. This is the only place I've ever heard of this happening. And I still don't know what the folder is actually doing. Has anyone come across this situation? Do you know what that folder is actually doing? Or, is there anything I can do to work around it? Thanks! Dan Waters -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com