Server Authentication and SM

[Tissot]

Hi,

I've just been splitting our Solution into SM (Separate Model). There are about 10 DB containing all the Data hosted on a W2k3 Server with FMS. I've now got one GUI file for the "Client Side" getting info from the FMS.

The Problem is that the users are getting 10 Login boxes at start up, because obviously the FMS Authentication only works when the File is hosted on the Server.

Has anyone come over this issue? How can I make it so the user only enters his/her Login info ONCE?

Regards

Ron

PS: Why so many Data files? Because I've got several File Managers running on the Server and I want them separate.

[Steven H. Blackwell]

Has anyone come over this issue? How can I make it so the user only enters his/her Login info ONCE?

By placing the UI/Logic file on the server where it is really supposed to be.

Steven

[Tissot]

But thats the whole idea of it !?!?!?

So there is less trafic + you can make different UI for different Users.

Did I totaly miss the point here?

Ron

[Steven H. Blackwell]

Did I totaly miss the point here?

Pretty much, sorry to tell you.

The Separation Model™ (TSM) has as its underlying principle the architrctural separation of data, logic, and presentation. One of the principal benefits of such a construct is that the UI/Logic layers can be updated without having to touch the data layers.

[color:red]Nothing about that model mandates the placing of UI or logic files on the local workstation.

Steven