This is little off from the orginal post, but interesting what you said here. Let you know that at one time with FPW 2.6, I had to update the tables and even send messages to other end-user viewers to let them know the data is updated while they are looking at the older data. Furthermore, it was all in DOS, yet, I also had to make this both available in DOS and Windows, even to let it be while one using Windows and other using DOS (not DOS shell thing) at the same time (had to use NetBEUI or something, boy it's been so long ago already?), all that, quite something, isn't it? What happened to VFP now? <g>

You mentioned framework, was it "home-made" or something like CodeMine?

Chuck

>Are you using forms with private datasessions? If so, then opening the data in the default datasession will not allow you to see the data in the forms. The same is true of the various SET values (Set Exclusive, Set Deleted, etc.). They are scoped to the datasession.
>
>Another problem with opening all tables in the default datasession is that you cannot always get the latest data from the server/hard disk. Your forms, even with private datasessions, will use the "USE MyTable AGAIN" syntax, and data another user has saved to disk will not always show up on your workstation. We spent many hours tracking down this problem in a VFP5 app where our framework had opened all tables in the default datasession "to speed up form loading".
>
>The table holding our unique IDs was not updating, despite our closing it and re-using it every time it was called. Then we got duplicate ID errors. Removing the auto-load from the main program solved the problem.
>
>>I don't know about you or others, but I avoid DE. I only use it during creating the form(s) to use the droplist, but that's about it. So, my suggestion is (as this is what I do) is open ALL tables in SHARED (just SET EXCLUSIVE in the beginning of a main.prg is enough) and (also in beginning of main.prg) CURSORSETPROP("Buffering",3,0). Don't "just do it" until you know about it...