I'm in the learning process of using HTML and OECGI, accessing OpenInsight 4+. If I have multiple companies accessing the same database table structures but different data, how do I establish this? I guess I'm looking for something like a sign on page that propmts for user name and password, then attaches the tables based on the users login. Again, I'm new to this. Perhaps I have the concept wrong. Any help would be appreciated.

Thanks.

Charlie

Charles,

I would go with the login process that would determine which datatables that user should access, but I'm not sure about attaching tables on the fly. It would be easier to have all the datatables attached and ready to go. Also with the OECGI able to handle multiple requests, you could have multiple companies accessing each table simultaneously.

If the data structure is identical, you could have a single online form for easy data entry. You would need to point the online form to the appropriate datatable before a read or write is physically done. In order to determine which datatables the user would need to access, be sure to include the Company ID as part of each http link or as a hidden entry field in an online form.

Hope this helps,

psimonsen@srpcs.com

SRP Computer Solutions, Inc.

Thanks for your feedback. Do you have any guidelines for creating a login screen via the web. I couldn't find any material on the website or in the tutorial. Again, thanks.

Charles,

I don't think you will find much in OI documentation on designing a login screen. The easiest way would be to use an HTML editor or create an html file manually to design your login window. Have the login form submitted to a custom Inet routine through the OECGI. This routine will need to parse the username and password then compare it against some kind of user table.

If you are comfortable creating html files you can also view the source to existing html login screens to get an idea.

Hope this helps,

psimonsen@srpcs.com

SRP Computer Solutions, Inc.

Charles,

You could password protect directories. One for each customer. So you can have your customer access that one password protected directory. Once there the customer then can do the queries. Using the HTTP_REFERER option, you can check where the query came from (the complete address). If the query came from the correct directory, well it is believable that your one customer has made the request.

Lets call your website "aaa.com", call your customer "custa". So the directory for that one customer would be "/customers/custa". Or the customer would access their web page on your server as "www.aaa.com/customers/custa". The login id and password comes up for them to enter the data. If they answer correctly, they get access to the directory.

You have now uniquely identified that customer, and that customer has "logged in" (using a userid and password).

The actual login and password prompt would look almost identical to the one you get when you access this discussion board.

The way to set up password directories is different based on the type of web server you are using.

Richard, thanks for the helpful comments. I'll give it a shot.

View this thread on the Works forum...