🚀 go-pugleaf

Hello all

I am about to embark on building a 5 user application using SQL Server 7 but
before I start I wanted to get some general advice to ensure that I am
essentially adopting the correct route.

The SQL database will be stored on a server machine with five
implementations of the client application accessing the database. There is
to be no middle tier, just SQL Server and the clients.

I am using ADO since it seems to be the only option to take advantage of the
new datatypes in SQL Server 7. Am I correct?

The main piece of guidance I need is with regard to the data sets. I
understand that ADO Tables and Queries always return a Live result set. Is
this correct?

I am also given to understand that a user can make inserts, deletes etc
through the standard ADO Table components and Query components.

I am keen that when User 1 adds a record to a table, the updated table is
reflected in the interfaces of the other 4 user's applications. (Similarly
with deletes, edits etc. etc.). Does the fact that ADO returns live datasets
mean that this will happen automatically or do the sets need to be refreshed
from time to time, perhaps using an OnTimer event?

Should I be using Server Side Cursors in the properties of the
Tables/Queries and set the Cursor Type to dynamic to achieve the desired
result in the other user applications?

If I am developing partly on my work network and partly on a stand alone
machine, I think I'm right that the server side cursors and dynamic type
cursors may not work correctly on a stand alone set-up. If this is so, is
there any way to achieve a reliable development platform on the stand alone
environment. For example if I run two instances of the user application on
my stand alone set-up, I would like to see that changes to the database made
in one user app are reflected immediately in the interface of the other.

I look forward o some guidance and thanks in advance for your help.

Regards

Ian Searle