Memo problem

We have a memo problem.
At work we use P11 in a network with 3 PC's.
1 of them with XP-SP2 and P11 (and P11runtime), the other 2 are W98 PC's
with Paradox runtime11.
BDE 5.1, LocalShare set TRUE, also followed the "EnableOplocks set to 0...."
They are all 3 connected to a switch. The tables and forms are located at
the XP PC. This XP is also in use as a PC (we know its not ideal).

One of the forms is using 8 tables directly (with UIObjects).
The most often used table has about 13.000 records, 15 different fields and
one of the field is a memofield with 100 characters in de DBfile directly.
The problem is that Paradox on the XP seems to "lose the connection" with
the file with the MBextention. It does not happen allways but several times
a day.
When you open the form at the XP, and look at the memofield, there you can
see wat's in the field and you can edit it.
But after a while, sometimes after scrolling the table of do a locate on one
of the (other) fields, you still can see the value of the memofield but it
becomes blank when try to set the cursor in to it. If then setting the
cursor in a other field the value appaers again. This only happens with a
memovalue with more then 100 characters (i asume it only then uses the MB
file).
It happens only at the XP but in Paradox 11 and also in Paradox runtime 11.
It makes no difference if the other W98-PC's are on or off.
When closing and re-open the form on the XP the problem is gone (for a
while).

When the problem happens and a locate asignment is done in the memofield an
error arives "Unexpected Stack Overflow. Press 'Ok' then save your doc...",
followed by "Unexpected General Protection Violation. press''OK' then
save..." .
When the problem occurs and then at the same time we open the table directly
(without using the form) the memofield also becomes blank when try to edit.
When the problem occurs and then at the same time we use the form at a W98
PC there is no problem we can still edit the memofield.
If we try to put new data in the blank memofield we mostly have to do a
rebuild of the table.
Once i saw a error named "Not exact read/write, Tabel
G:\Paradox11\Tabellen\Werkbonnen.MB,
File:G:\Paradox11\Tabellen\Werkbonnen.MB"...
It looks like a network problem to me but we have no idea how to solve the
problem. The problem came together with a new PC with XP and P11 and the
switch (before that we used 2 W98 PC's with Paradox8 and a direct
cable-connection, there was no problem).
Any suggestions are very welcom.

Ton.


.

Relevant Pages

  • Re: Slow Accessing a memo field on a network
    ... memofield into a local variable one time and then process the information ... Is this a network or maybe a VFP issue where in a shared file it ... I played around with my memo field and I ... same table open on a second workstation that it could then take some ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Slow Accessing a memo field on a network
    ... It's pretty normal for database access across the network to take as much as 10 times longer under multiuser. ... I just can't see being able to open a form in under one second and then if I have that same table open on a second workstation that it could then take some 5-10 seconds to open that same form. ... It must first ask Windows to poll the network to see if other users have cached changes that must be updated to the server and then updated to the local cache. ... I understand that the memofield access can be slow ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Slow Accessing a memo field on a network
    ... Part of best practices over a network is to not do more reads ... on a second workstation that it could then take some 5-10 seconds to open ... I understand that the memofield access can be slow ... It drastically speeds up ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Slow Accessing a memo field on a network
    ... I don't think their network has this problem but I'm going to go ... the server and then updated to the local cache. ... I understand that the memofield access can be slow ... is it so much slower when the file is open at another workstation on ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Slow Accessing a memo field on a network
    ... multiple reads from the same field (reading the memofield about 150 times) ... Is this a network or maybe a VFP issue where in a shared file it internally ... I played around with my memo field and I noticed ... open on a second workstation that it could then take some 5-10 seconds to ...
    (microsoft.public.fox.programmer.exchange)