Paradox, BDE - Open tables slow on big networks

[Nicolás]

I have an application using Paradox 7 with BDE 5.2. Usually (80% of
cases) works very well, 5 or more users working with good size tables.
Under some scenarios, with lower number of users, smaller tables and good
hardware, open a module (when open many tables) takes unusual long time...
but when the tables are opened, then the work speed is acceptable.

For example, now I have a case with only 2 PC (both Windows XP SP2) using
Paradox tables under these conditions. The PCs have users of a domain.
Some times open a module (that open many tables) takes very long time and
is very difficult work, if the other user is using the tables, can take
more time. The user reports that usually in the afternoon the problem is
more evident. The user say to me that the problem begins after migration
from Windows NT to XP...

The users can't change to work under a simple workgroup, they are under
the administrator control and eventually use other resources of the
network with controlled permissions.

Usually I can see these delays under big networks scenarios, with areas,
sections, groups, etc.

Then, I think... may be all is ok in a network under a workgroup, and the
problem is under domains? slower in proportion with the quantity of
stations under de Active Directory?

Anybody see cases like these? there is a solution?

Thanks!!

[Bill Todd [TeamB]]

The only real solution is to replace Paradox with a database server
that is designed to easily replace Paradox tables. Advantage, NexusDb
and DBISAM are three possibilities.

You could also move to one of the many SQL database servers but this
will require some application redesign and will more difficult.

File server databases like Paradox are very sensitive to network speed,
network traffic load and applicaiton design in a multi-user
environment. Your description is typical of what happens when network
load increases.

--
Bill Todd (TeamB)

[Nicolás]

Thank you for your reply Bill. I agree with you and I was thinking about
these solutions (especially NexusDB).
The problem is that there are no plans in the immediate future to make
changes in the application. I am not going to bore explaining the causes.

If something can be done should be done using Paradox.
Anyway, thank you.

[Joseph Gordon]

I don't know if this helps but I have had large slow downs on
some systems where the Anti-virus software was continually
checking. I disabled it and things went a lot faster. Then I
was able to determine that it was checking *.db files and
remove them from the files to check.

You might also try the usual suspects like increasing the MaxBufSize
to something big like 49152 in the BDE Admin and see if you see an
improvement. I have also heard of someone that had a screen
saver on the server that did slow 3d graphics and anytime the screen
saver went on it slowed the server down, when the server was
checked, which caused the screen save to disengage, it looked fine.

Thanks,
J. Gordon

"Nicolás" <nico...@gmail.com> wrote in message
news:op.uebl4n1nxqyrve@waly6lx...