We are new to OpenInsight, however, we have two very good AREV programmers and so far we can?t come up with a solution.

There are many users in the same office that needs access to various applications. Our old AREV system has around 30 applications.

Our plan is to develop a common opening IO screen/form that will be in a system called START (or some other name). This form will determine what applications a given user can access and display, in a checkbox format, only those systems. Example: User A has access to the following applications: ACT, DTK, INV but not DMS, AGT and JIM. Only ACT, DTK and INV will be displayed to User A. User A selects DTK.

The problem is that our common screen is in the START system and the user needs to get to the system called DTK where all the necessary screens/forms/files are located. How to we transfer control from the START system screen/form to the first DTK screen/form?

Any ideas??

Thanks

Andy Becker et al

Illinois State Lottery

Would it not be easier to attach ALL the tables in one application and control access from one application - remember OI can attach tables in applications that don't belong to "it".

The Sprezzatura Group

World Leaders in all things RevSoft

We can see how this would work for data but how would we logically manage the individual system's screens/forms? Physically it's one large application with many sub applications. We don't want one application having access into another application's information. We don't want all the screen/forms in the same application. We also have the need for the user to be able to have multiple applications open at the same time.

Andy,

Sprezz's suggestion is the best (and probably only) way to accomplish what you want. First of all, OpenInsight is single threaded and cannot have multiple copies running simultaneously (unlike what you are familiar with in AREV.) Second, you needn't worry about all the screens being developed in one application. Access to the system is not like AREV where there are many roads into TCL and the system files. When OpenInsight is launched as a runtime system all that your users see are the screens they've been given access to. You would simply design a security system that would allow only certain buttons or menus to be available to your end users. We've done this many times and it all works well.

dbakke@srpcs.com

SRP Computer Solutions

Andy,

I forgot to mention that if you are running all NT Workstations then you can probably run multiple copies of OI as long as they are in separate memory locations. Of course this will take an additional user for each instance.

dbakke@srpcs.com

SRP Computer Solutions

Thanks Don - and Win2000 of course - I'm sitting here now doing exactly that!

Another way is to change users on the fly and attach diffewrent databases but it is a PITA to be honest.

The Sprezzatura Group

World Leaders in all things RevSoft

Thanks for all the input on this problem. We are currently revamping our design. You saved us a lot of grief.

Dave:

Thanks for your input on this problem. We are currently revamping our design. You saved us a lot of grief.

Dave is my father. You must have us confused, although we don't really look alike…

View this thread on the forum...