I have a solution that I'm working on, using FMP 6.04 on MacOSX. Eventually it will end up as a runtime on a workstation that is part of a WinNT network, with various users logging on to use the machine and the solution there.

Can someone tell me what the Status(CurrentUser) field will return in this scenario. The FMP manual says it will return the name of the user set in the application preferences, however I feel sure that this wouldn't be the case for a runtime solution.

I am expecting that it will give the name of the logged on user (WinNT user name) - at least I hope it will as this will make my life a lot easier.

Cheers, Murray

Hi,

A runtime has its very own 'Application Preferences', just like the 'mothership' does.

...and I'm afraid that the Status(CurrentUser) function operates within a runtime very much the same as it does within FMP itself, returning the user name which is stored in application prefs for the runtime.

If you want to gain a higher level of control over the process, you might like to check out the DialogMagic plug-in from NMCI, which will allow you to write to the app prefs via a script. If you were to then use VB or some other method to capture the current logged on user from the NT shell, you'd be able to sync the app prefs with the network and then get the result you want. However it's a lot of work for a small return, and you might be better off setting up a custom login system within your runtime instead.

Thanks Ray,

By a custom login, do you mean have passwords assigned to groups, and groups assigned one per user so that I can use Status(CurrentGroups) to identify the user? I think I may have to do this because I want to set editing privileges so that only the creator can edit their records.

If this is the case I think I know how to do that (only through reading these posts of course!).

Cheers, Murray

PS. Whose name would be stored in the runtime preferences - the developer that binds the solution??

Hi Murray,

That's not exactly what I meant - but it is another option which I perhaps should have thought to mention.

If you pre-install a separate password for every user and assign each to it's own separate group, you'll be able to identify who logged in by using the Status(CurrentGroups) function. Bear in mind, however, that it's possible to assign a password to more than one group (and unavoidable in the case of a master password, which by necesesity is assigned to all groups simultaneously), in which case Status(CurrentGroups) returns a list of groups separated by CRs.

By custom login system, however, I meant a user identification procedure of your own, implemented by setting up a databse as part of the solution which stores user details (including their password, preferably in encrypted form).

As to app prefs for the runtime, it will work the same as in a full copy of the desktop FMP application. The user will get to enter a name of their own choosing when they first launch the runtime after installing it on a given machine - and will subsequently be able to change it via Edit>Application Preferences if they wish.