(originally Delphi 1 och B-Tree 5.42, but I have updated it several times.)
The application has been running in several places during many years without
any major problems.
Now when compiled with Delphi 6 and B-Tree Filer 5.55 I get network
problems, typical IsamError 10332.
Sometimes immediate, sometimes after several hours.
This installation has around 5 to 10 users, all with Win 98. Some of them
can work, some they get
IsamError 10332. Is seems to be random, who will get the error.
With an earlier version, almost the same code, just some minor changes done,
compiled with Delphi 4
and B-Tree 5.54 there is no problems. They have changed back an forth, the
old version works, the new
does give them 10332.
They have tried NetSafe. They still get the same problem.
Please help! Anyone having a similar problem.
Torbjorn Gerhardsson
Sweden
> Now when compiled with Delphi 6 and B-Tree Filer 5.55 I get
> network problems, typical IsamError 10332.
Did you download the BTDEFINE.INC update from the TurboPower Foundry?
B-Tree Filer v5.55 actually only supports Delphi up to version 5. The
BTDEFINE.INC that is in the Foundry adds support for Delphi 6 and 7. (If
you're using the FvcBrowser, you'll also want to download the B-Tree Filer
packages for Delphi 6.)
--Rob [TPX]
> I have downloaded the BTDEFINE.INC with support for Delphi 6 and 7, so
that
> should be OK.
>
> I have been using a modified version of FvcBrowser for many years, so when
> an update comes I compare the standard unmodified source before and after
> the update, and then I make the same changes by hand in my modified copy
of
> FvcBrowser.
>
> So it should be pretty much the same as the standard FvcBrowser.
>
> But I did not recompile my modfied-fvcbrowser package, I just rebuild my
> application ("Project", "Build"-command). Shouldn't that be enough? I
> distribute my program as a single exe-file.
I'm not sure whether you need to recompile your modified FvcBrowser package.
I would do it just to be on the safe side. If you still run into the lock
errors after that, then the only other thing I can think of is the Windows
caching problem. You said that you're using NetSafe, but are you sure it
has been run on every workstation? If even one workstation isn't configured
properly to prevent the caching problem, it can result in lock errors and
data corruption. I've had many problems with this, where network
administrators at my clients' sites claim they have run NetSafe on every
machine, but they often miss one or two. For this reason, I've added
startup code to all of my B-Tree Filer apps that checks for proper
configuration and refuses to open the data files if things aren't right. (I
modified the code from The Delphi Magazine article "Paradox File Corruption"
for this purpose. You can read the article at
http://www.thedelphimagazine.com/samples/Paradox/paradox.htm.)
--Rob [TPX]
> But still, if this is a classical problem, if they have bad setttings,
they
> would have problems with the earlier versions of my program too (like
> Delphi 4/B-Tree 5.52). Wouldn't they?
Yes, if they didn't have things configured correctly they would have
problems with your older versions, too. But maybe they just hooked up a new
workstation and didn't run NetSafe on it, or messed with some settings on an
old one, or re-installed Novell Client 32. (Just guessing, because I don't
have any ideas other than the Windows caching problem.)
--Rob [TPX]
I have downloaded the BTDEFINE.INC with support for Delphi 6 and 7, so that
should be OK.
I have been using a modified version of FvcBrowser for many years, so when
an update comes I compare the standard unmodified source before and after
the update, and then I make the same changes by hand in my modified copy of
FvcBrowser.
So it should be pretty much the same as the standard FvcBrowser.
But I did not recompile my modfied-fvcbrowser package, I just rebuild my
application ("Project", "Build"-command). Shouldn't that be enough? I
distribute my program as a single exe-file.
Thank you in advance
/Torbjorn Gerhardsson
"Rob Roberts [TPX]" <do...@email.me> skrev i meddelandet
news:78c1JOfo...@tpsmail01.turbopower.net...
But still, if this is a classical problem, if they have bad setttings, they
would have problems with the earlier versions of my program too (like Delphi
4/B-Tree 5.52). Wouldn't they?
Thanks again.
Torbjorn Gerhardsson
> Yes, if they didn't have things configured correctly they would have
> problems with your older versions, too. But maybe they just hooked up a
new
> workstation and didn't run NetSafe on it, or messed with some settings on
an
> old one, or re-installed Novell Client 32. (Just guessing, because I
don't
> have any ideas other than the Windows caching problem.)
It seems like it all depends on the new compilation.
History: Everything is OK. Update: Problems almost immediate (IsamError
10332). Reinstalled the old version. Run for two week without problems.
Tried another time with then new version after having run NetSafe on all
computers (included the server). Installed the new version: Problems after a
couple of hours (IsamError 10332 or just hang). Reinstalled the old version:
Running without problem for a week now.
=> It seems the problem arise with Delphi 6 and B-tree filer 5.55 (and no
problems with Delphi 4 and B-Tree Filer 5.54 ). Funny...
Grateful for any more suggestions or ideas.
Torbjorn