Shared Database Help please

[Serincino]

I have pushed my app to all my workstations. Everything seems to run smoothly except for that every once in a while when a workstation does a search or access a database some or all the files are missing, but if another workstation does the samething at the same thing right after everything is as should be, the only solutuion thus far is to completely exist the app and restart it. Does anyone have any ideas as to what would cause this. This is a live enviroment and I need a fix fast. Thanks for all the help in advance and for all the help this forum is given in the past.

-Serincino

If you see a programmer in the office before 9am, they probably never left.

 

[Serincino]

I almost forgot. The app is written in VFP8.0 the databases are accessed through a share on the server that is mapped to the Z: drive on the workstations through a .bat file that is run as a script through my domain controller when the computers boot up. (Using active Directory Windows 2003 Server and the GPO applies the script)

If you see a programmer in the office before 9am, they probably never left.

 

[craigsboyd]

Serincino,

Wehn you say that "some or all of the files are missing", what do you mean exactly? Is there an error thrown? If so, what is it? Is the program acting like it can't see the tables or can't see the records inside? When you say "Search or access a database", what do you mean exactly? Is there specific code that you are using to access the database and do searches that is causing this behavior? If so, can you provide an example of that? Is the problem readily reproduceable? Is the problem on one workstation or do all of the workstation exhibit this same behavior? Since the workaround you are using right now is to shutdown the application and restart it, am I safe in assuming that once the application starts to exhibit the unwanted behavior that it will continue to do so indefinately unless you restart the application? Did the application work fine at one time and now all of a sudden this behavior has started? If so, has anything been changed on the workstations or on the server and what were the changes if any?

Slighthaze = NULL
[sub]craig1442@mchsi.com[/sub][sup]

"Whom computers would destroy, they must first drive mad." - Anon​

[/sup]

 

[Serincino]

"some or all of the files are missing", what do you mean exactly?

The program continues to work normal and act as if it is using the database as it should, but seek return a !found()
and in browse or grids that are supposed to display the data they are blank.

Search or Access a Database?
Search I mean it uses a seek and access I mean it switches work ares like Select J where ledger1 is loaded.

The problem is not reproducialbe that I can find, it just happens every once in a while on different stations.

This has never happened before, this is the first time the program as been used network wide and the file not being stored locally.

So far not all the stations have exhibited this behavior only 2.

As far as I have tried no matter what I do after the workstation starts the behavior it continues to do so.

The biggest change to the enviroment is that the program is now accessing the databases across the network and the app was developed with everything locally. Also the databases where never being accessed by more than one app at a time during development or testing.

If you see a programmer in the office before 9am, they probably never left.

 

[BPeisch]

I think you're dealing with two different problems here. First, the seek that doesn't find a match. Have the users run a process that has SET EXACT ON, and left it that way? Unless you're doing a SEEK on the exact string in the index or have SET EXACT OFF, you won't get a match. There are techniques for debugging a SEEK that fails, but it's hard to do if the problem happens so rarely.

As far as a grid being empty, is it totally blank, meaning the grid lines are gone too, or is it just not showing any data? If it's totally blank, you've probably ripped the recordsource out from under the grid at some point. Grids are temperamental, and don't like that. If you use a view as the recordsource and just Requery it, that shouldn't be a problem. But if you use a cursor, and rebuild the cursor, you'd better set the recordsource to '' first, and set it back to the cursor after you rebuild it.



-BP

http://www.peisch.com