Hello again,

Now I have a working form, a few things spring to mind.

Should I use ZZCGI if the web application I plan to use would have a large number of hits from many different users?

What are the differences between OECGI and ZZCGI?

How would the DB handle many user accounts?

Concurrency; presumably I would be advised to implement some form of locking if many concurrent users would access a set of tables?

What do you advise in terms of locking? Does the OI DB provide any concurrency control built in as it where?

Briefly here is my idea:

I would like to be able to give a set of tables for each customer so they have their own data. Now this customer will have many people (users) who would need passwords to control access to their particular views of the data. For example I wouldn't want anyone in sales to be able to view the employee records to see what their colleagues are getting paid - just an example!

Apologies for all the questions but that's what happens when you start learning a new (to me) DB technology.

Thanks in advance,

Ian

some of my opinions…

1) Concurrency… locking. Check out the "lock routine" or "lock statement". They do exactly what you are asking for. It is critical to "lock" rows while updating or modifying.

2) Giving a set of tables for each customer… There are a couple ways to do it. Check out the "alias_table" or "attach_table". They will allow you to selectivly access tables. You could use the user login information to determine what tables to attach.

3) Passwords to control access to particular views of data… There are several way to do this also. You could password protect each form. The form's create event is quite useful for this. You could encrypt the data in the tables. A file MFS would allow for that. You could restrict using selective menus for each user, user type, or department. Creating context menus would do that. I use a method quite like the windows start button. Items are disabled or hidden based upon the user login information.

4) Differences of OECGI and ZZCGI… I can not answer that. Although I do have a web application that handles Imaging indexing and document retrieval. So I would imagine what you are planning is quite possible.

You as the programmer have many available ways to handle the above items. I guess that is where experience will come in handy.

I notice you are not a "works" member. You might want to start there. Being a "works" member does have its advantages.

Hi Ian

ZZCGI is designed to allow multiple entry points into the same copy of OI - so foe example if you had an application called SALES and an application called PERSONNEL ZZCGI would allow you to log into either depending on the URL you specify. OECGI would only allow you to log into SALES OR PERSONNEL - it is a single entry point solution.

The DB will allow you to implement as many accounts or users for accounts as you want.

For a large number of hits we recommend S/Web. This is in active use with sites experiencing millions of database hits a day and is very scaleable. It also has built in concurrency control which by default starts off pessimistic and drops to optimistic after a developer specified interval. The problem with a pessimistic lock is the standard one that the remote user may go for lunch without undoing it! We would recommend SOME form of locking however implemented!

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

View this thread on the forum...