Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Data Display on Forms
Message
De
01/11/1999 20:57:12
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00284357
Message ID:
00285225
Vues:
19
Barbara,

I appreciate your help and I finally bit the bullet on your last suggestion (closing/opening tables) and changed how all the forms worked. It took awhile to get it right, but darn if that didn't do the trick!

I just would really like to understand why it doesn't work the other way and if there is a better way to do this. I can't believe with buffering in a multi-user app, that most developers have not run across this more often. I've talked to quite a few and they didn't know anything about it and I cannot find any kind of reference to it on MS's Knowledgebase.

It's working and once I get it thru Quality Assurance, then I can move on. If you come across any further info on this topic, I'm sure interested.

Thanks again!

John

>I've run into this on 2 systems, both NT Server (although that may have nothing to do with it). On one we only needed a single file and we opened and closed it as needed. The other was more complicated, using views, so we ended up doing a requery() IF a file on the server had been updated. Part of our SAVE routine on the 3 tables involved was to update the file.
>
>This SHOULD be handled by the refresh, but I couldn't get it to work.
>
>Barbara
>
>>Barbara,
>>
>>I've made sure the default datasession has now tables open.
>>I've got the Refresh down to 1,1
>>I've refreshed the forms in the activiate event.
>>
>>I do not reopen the tables. I open them in the dataenvironment, set to optimistic row buffering. The same table is open in the parent form and is also set to optimistic row buffering. When I view the same form on two different pc's, the same data show different on both. It looks ok on the 1st pc that changed it, but on the 2nd pc it still looks like the original.
>>
>>I do not understand. This is straight open the table in the dataenvironment, private datasession, update it, unlock it and release the form. I cannot see why the other user see's the original values.
>>
>>I really was hoping I did not have to managing opening and closing the table outside the dataenvironment.
>>
>>Anything else I can do before I go to that extreme?
>>
>>I appreciate your help and info.
>>
>>John
>>
>>
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform