🚀 go-pugleaf

Hi all,

I have a deployed app running on a network with about 4-5 active and 6-8
occasional users. Its purpose is to maintain clients, job orders and
bills-of-materials for a printing company. The app (written with VdB
5.5a) is installed on each workstation with the tables located on the
server. There are 15 tables in use with 13 of the tables related to one
another by set relation statements in the qbe. All tables and relations
are set as the main form (to browse clients) opens and are maintained
for use by some 30+ child forms.

Performance is excellent with one or two users. Above that, performance
goes to you-know-where in a hand basket. Their network consultant
reports very high net traffic when the app does certain operations. My
suspicion is that record pointer movement from all the required
relations is the cause. The consultant suggested I convert to SQL as a
means to reduce net traffic. Most users run Pentiums with 32mb RAM (60%
Win95 / 40% WFWG).

Before re-writing the app for SQL (assuming it can be done in 5.5a/5.6),
I would like some assurance that using SQL to access DBF tables in a
5.5a app will actually result in a significant reduction of net traffic
for the same conditions. I don't fully understand the mechanics of SQL
vs. normal DBF access, so I am requesting your help. Is SQL better or
worse? Can you give any reasons as to how or why? Will it be worth my
time (literally) to make the conversion?

TIA, John

BTW, VdB7 is NOT an option for this app (at the present time).