From: Harrisjr@bwsc.org
In an earlier posting I said that I would try eliminating GPVs via a User
that is getting GPVs all day by asking her to place the Task Bar at the top
of the screen and maximize Paradox.
THIS DID NOT ELIMINATE GPVs.
Last night I did 3 things:
I CHANGED Local Share from FALSE to TRUE
VERIFIED all tables
One table WAS CORRUPTED but repaired without losing any data
The corrupt table - is an Item # table used on MANY forms
Chances are good this table was CORRUPT when I last PACKED
PACKED all tables
I will wait a few days before asking Users about GPVs.
In the meantime I am going to ask the Network Administrator to:
Set OplocksDisabled to 1 (TRUE)
Set EnableOplocks to 0 (FALSE)
MAKING THIS CASE…
NetWare and Linux both need oplocks turned off, regardless
of workstation OS
Once ALL of your workstations are using XP the above MAY NOT NEED to be set
BUT if there are NON-MICROSOFT products on XP workstations it is best if
the above is set
Another complaint I am getting from My Pdox Users is that their workstation
sometimes freezes and throws them out of Paradox – no error message. BUT
this only happens after 5PM. They thought it was OK because maybe backups
were being done.
I checked with the Network Administrator (NA) and was told YES backups are
done after 5PM BUT should not interfere with Users if they are online.
Reading what the NA said about OPLOCKS:
To improve performance, Windows 2000/2003 Server by default enables and
uses
opportunistic file locking to allow workstations to read more database
records than
they currently need. This read-ahead can cause database corruption when
workstation
B modifies the record previously read by workstation A, then workstation
A does not
flush the invalid data from the cache.
To reduce the possibility of database corruption, Microsoft recommends
disabling
opportunistic file locking in networks that have any workstations with
Windows 98
Second Edition, Windows ME, or Windows 2000 Professional with Service
Pack 1 or
Service Pack 2.
You do not need to disable opportunistic file locking if all of the
workstations
in your
network have Windows 2000 Professional with Service Pack 3 or higher or
Windows
XP Professional
It would seem to me that setting the OPLOCKS as stated above would cause
NO PROBLEMS and may even solve some problems.
Maybe this is the reason why Users are thrown out of the system.
I will POST in a separate thread after GPVs is solved or accepted as ‘a fact
of life’…
Peter Rousseau wrote:
>Hi Jeanette:
>One thing that happened to me recently:
>I have a calculated field on a form. I changed some field names of the
>associated table and when I reopened the form it came up in design mode
>and displayed the problem (in the editor) that the field name was not
>valid - normal & expected result. I then changed to the new field names
>and I got a gpv. I next tried a diferent appraoch: closed the editor,
>inspected the field and chose "define field", deleted the old names and
>"copied" the new fields from the drop down list. I still got gpv's. I
>ended up deleting the field and rebuilding it.
>
>I guess my point is have you modified anything on the form? Perhaps
>deleting and rebuilding will fix it.
>
>Peter R
>
>
>Jeanette wrote:
>
>>Bertil,
>>
>>My Users tell me that they are not using any particular screen or running
>>any particular process when the GPVs occur. Based on the postings I’ve
read
>>I have asked one Super User to move her TASK BAR to the Top and Maximize
>>Paradox to see if that will eliminate the GPVs. If it does eliminate the
>>GPVs I will add to my Main Menu screen’s init method
>>ShowApplicationBar(True)
>>sleep()
>>ShowApplicationBar(False)
>>
>>I hope that Jim Moseley will give this a try and let the NewsGroup know
>>if it eliminates the GPVs his Users have been getting for 2 years!
>>
>>
>>"Bjorn Sagbakken" wrote:
>>
>>
>>>"Jeanette" wrote in message
>>>news:466d57ab$1@pnews.thedbcommunity.com...
>>>
>>>
>>>>Good Morning,
>>>>
>>>>My Paradox 'ALL DAY' Users are getting GPVs all day - everyday.
>>>>They tell me they are not doing anything in particular when the GPVs
>>>>occur.
>>>>We have had Paradox 9 for several years without GPVs.
>>>>The Paradox App is loaded on Windows XP SP2 PCs.
>>>>The database sits on a Window 2003 R2 SHARE Machine.
>>>>
>>>>Can someone tell me why this is occurring and how can I stop the GPVs?
>>>>
>>>>
>>>I totally agree. This message comes all the time, but mostly the user
can
>>>
>>>
>>
>>
>>
>>>continue, so ignore the message is what I tell my users. Only if the
>>>computer starts to burn, there is a real problem.
>>>
>>>If I didn't know better, I would say that Paradox sucks, but I know it
is
>>>
>>>
>>
>>
>>
>>>fantastic in its way. I still develop various stuff, but I am gradually
>>>
>>>
>>
>>
>>
>>>converting our data from Paradox to SQL while building a .NET web
>>>application to take over the userinterface. This is no easy task, but
since
>>>
>>>
>>
>>
>>
>>>Paradox 11 seems to be the last one we can expect, I am planning a two
year
>>>
>>>
>>
>>
>>
>>>phase out with champagne at the end and a few sad tears for something
that
>>>
>>>
>>
>>
>>
>>>could have been a success - but died.
>>>
>>>I remmber the summer sunny days early in the 1990's I was lying streched
>>>
>>>
>>out
>>
>>
>>>in a park with cold beer at an arms length, reading the manuals for Paradox
>>>
>>>
>>
>>
>>
>>>for Windows version 1.0, thinking this must be a golden path. I was totally
>>>
>>>
>>
>>
>>
>>>convinced I had choosen the ultimate database software, and truly enough
>>>
>>>
>>I
>>
>>
>>>performed miracles for our company in the years to come.
>>>
>>>Well, the adventure didn't last forever. Now it is an old horse.
>>>
>>>Bjorn
>>>
>>>
>>>
>>>
>>
>>
>>
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
