Windows / Paradox Cashing?

[bigandfat]

I have writen forms and queries and saved them on a server. The user PC's access the forms, queries and tables from the server. I am finding that either windows ( 2000 Pro ) or paradox ( 10 Runtime ) is saving old versions of my forms and queries on the user pc's even though I have updated the versions on the server.( Ie: if I change the date range on a query and save it to the server the user pc continues to run the prevoius version of the query which no longer exists on the server!)
Does anyone know of a knowledge source that explains this situation?

Thanks in advance

 

[Langley]

The first thing I would check is your idapi files and make sure that everyone's aliases are pointed to the right place on the network. Short of that being the problem, the only other thing I can think if which might give those results is if you have people working in the :WORK: or RIV: aliases and those are tied to the local machine. One more thought, make sure everyone is using the delivered (*DL) versions of your forms/reports, and make sure they are current. If your code calls forms/reports and you do not specify an extention (i.e. MYFORM.FSL or MYFORM.FDL for forms), I think it defaults to the FSL version.

Mac

"Do not delve too deeply in the arts of your enemy and so become ensnared by them"

langley_mckelvy@cd4.co.harris.tx.us

 

[footpad]

B&F,

What are you using for your networking software? If Microsoft NEtworking (or other peer-to-peer), you should also check the LOCAL SHARE setting on all workstations, especially the server.

To do so:

1. Start BDE Administrator (in Control Panel).
2. Click the Configuration tab, choose System | INIT, and then verify that LOCAL SHARE is set to TRUE.
3. Apply your changes and then restart all BDE applications.

If this doesn't resolve the problem, you may need to also disable write-behind (or similar) caching on the server. Paradox (or BDE) itself doesn't do a lot of caching on it's own. Generally, that's done by the NOS or the local copy of Windows.

Hope this helps...

-- Lance

 

[bigandfat]

Thanks for all you help, in the end it appears to be a windows cache problem. I suspect with Microsofts' internet mania the user interface handles desktop shortcuts like web pages and will save a copy ( if its small enough ) and will use that first. The paradox forms being small files end up being cached. If I deleat the short cut & recreate it things are fine.
Thanks again for all your help.