The Inside Sesame issues from December 2004 and January 2005 talk about creating a custom menu within an existing application that has multiple forms/databases.

What I am looking for is a custom menu that allows you to select an application, without having to see an entire list of applications available when you click on File, Open.

I am also trying to restrict certain users from seeing only the applications they need to see without having to set up multiple server sessions.

i.e. separate applications: Sales Calls, Top500, Clients, HR, Invoicing

I would like our Sales team to only see: Sales calls, Top500 and Clients.

Is this doable and is there any references to accomplishing this task ?

Thanks,

Louis

Bob Scott's suggestions are correct if you are trying to restrict access to DATABASES.  But your original request was about APPLICATIONS.  There is definitely a distinction in Sesame's terminology. 

In Sesame, the term APPLICATION refers to a pair of Seasame files, name.db and name.dat.  Each APPLICATION can have unlimited DATABASES within. 

In your original question, do you really mean APPLICATIONS, as defined here, or do you really mean DATABASES within an APPLICATION?  If you really mean databases, then follow Bob Scott's suggestions.  Also keep in mind that you can use the user ID to hide/display branches on the command tree in addition to using that for command buttons on a menu form.

If you mean Applications, per Sesame definition, you may want to consider making some batch files to start different applications based on user ID, etc.  Other "menuing" utilities may also be considered.

It is probably possible to make a Sesame Menu Page in a Sesame Application, per Bob's suggestion, that may allow you to open another copy of Sesame to run specific Sesame Applications, and close the one with the menu, but I think some type of batch files may be easier.

This was intended to clarify, not to confuse.  Hope it was helpful.  Good luck.

To answer Bob Hansen's question, my intentions deal with the Applications themselves and not specific databases within an application as per Bob Scott's suggestion.

Mark's suggestion to run multiple servers was one I tried several months ago but failed.  I am going to try this once again to see if I can make it work.

Mark (dumb question of the day):  if I have a "Sales Team" server, a "Client Support" server and an "Admin" server and they all need to access a common database such as "Clients", how do I point them to this common database given they are pointing to their specific applications ?

Thanks for everyone's input.

Louis

It should also be noted that, because they are using different servers, Sales and Manufacturing would need to take turns accessing the applications in the "Common" directory. It may be better to simply start a third server to access the "Common" directory and give both Sales and Manufacturing access to connect to that server (via client icons on the appropriate desktops).

Quote:

Yes. You can also use the SESAME_ROOTDIRS_PATH environment variable to control where Sesame looks for the file.

Quote:


Just the server.

Quote:


If you are actively trying to exclude people from having access to a particular server, you should assign unique (and obscure) port numbers to that server. If you have pre-assigned IP addresses (as opposed to DHCP) you can also use the allow and deny files to forcefully exclude access. Event with DHCP, if you partitiion your users across assigning routers, you can use the allow and deny files.