form design suggestions (forms 6i on 9ias)

[bookouri]

I currently use a "front-end" form to give users access to their various application forms. I present them with a form that has nothing but buttons that call other forms and reports. This has worked ok so far, but now the users have a new database they have to access. The users do not have the same usernames on the new database, so If I put a button to the new database with a call_form command, the form "automatically" tries to log the user on to the new database with the logon name they used when logging on to the "front-end". Is there any way I can force the call_form command to present the user with a logon screen so they can access both databases from the one front-end?

any other suggestions about the best way to provide users a consistent interface to get into their applications/reports would be appreciated...i elected to use a form front-end because it seemed like something the users could cope with. But I would be interested in hearing how other developers handle getting their users into their applications..

thanks for any suggestions..

 

[lewisp]

Have a look at using DDE.APP_BEGIN or RUN_PRODUCT(FORMS,....) instead of CALL_FORM.

 

[bookouri]

I used to use the run_product with forms 4.5 but I couldnt get it to work with 6i and 9ias. I never saw the dde.app_begin. Ill look that up..

thanks