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.

"Ton" <tonvanzuijlen (AT) planet (DOT) nl> wrote

first, bear in mind that memo fields are not as stable as regular paradox
table data.. and memos that are routinely modified are much more likely to
become damaged..

also, as you suggested, sharing the "server" as a workstation will cause
problems..

your descriptions indicate that you likely *do* have a damaged memo file..


--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox

Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards

Ton

On my site, you can find a document Errors Explained. Serach the index
for your errormessagae, Not exact read/write, and you'll find some
information.



--
Bertil Isberg
CTECH
Paradox Buglist: http://web.comhem.se/~u82608896/

remove spamfilter (reversed) to reply

Steven, Bertil,
Thanks for your reply.
Bertil, we did search before on your website for "Not exact read/write" and
saw some explanation. But this are other situations so we didn't become much
further.
From a Borlandsite we got the information its a errormessage from the BDE
its self but it doesn't explain how to handle.
We tried before to make up a new table from scratch and then apend the
records from the old (damaged?) table to the new one, but still the same
problem.
(Mayby we copied the problem). But if the memofile was damaged i think we
also must have the problem from the W98-PC's. They just work fine.
Mayby its a P11 problem handling with XP. We found out that Paradox11 has
strange bugs, most of them are mentioned in "Bertil Bugslist" but there are
more.
Anyway, thanks again, mayby some day we'll find the solution.

Ton.

"Bertil Isberg" <bertil.isberg (AT) retlifmapsSCB (DOT) se> schreef in bericht
news:43d75226$1 (AT) pnews (DOT) thedbcommunity.com...