Jump to content

This topic is 6457 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Is it for a single-user or multi-user runtime environment?

For a single user environment, I define all such fields in a separate "parameters" table and tie it in using the "x" relationship so they're available anywhere and everywhere. Maybe someone else can advise on the multi-user side.

Posted

Thanks.

The solution is to be multi user. 4 users on two machines. I plan to have each user login with an account name, but want to track some data specific to each user. Where they were when they logged out and the like.

Posted

Its a lot easier than you think. Create a global text field and set it to the user account name as part of the opening script.

Set Field [gUser; Get ( AccountName )].

You can now create a relationship from this global field to a table occurence of the UserTable. Now whenever you want to set a field with certain data for that user, you can allow it.

If you are on an nonrelated table, you may need to create additional table occurence of the orig table with your gUser as well as another instance of the UserTable TO.

Posted

IIf you are on an nonrelated table, you may need to create additional table occurence of the orig table with your gUser as well as another instance of the UserTable TO.

Could you explain this in a little more detail?

much appreciated.

This topic is 6457 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.