bankofbermuda Posted June 20, 2002 Posted June 20, 2002 I have a set of 3 databases: Clients, Interface, Files In my interface, I have a client search field which triggers a list of client names with matching string in a portal ("client name portal"). By selecting the relevant portal row, this will bring up the files for each client in a separate portal from the files database. I have a cbackground container in the client database which is a calculation: if(ClientNumber=Interface:tClientNumber, gBackground, "") The cBackground sits in the ClientNamePortal in the Interface and highlights the selected portal row. No Problem. However, in a multi-user environment. If two users are looking at the same list of clients in the ClientNamePortal then both users selections are highlighted to both users. Is there any way to limit the background container to only show the individual user's selection???
keshalyi Posted June 20, 2002 Posted June 20, 2002 Yes, and no. The best way I can think, would be to put a global repeating field in the background, as global fields are session-specific. This prevents several groucy, but I would think approachable problems (ie - what happens when you scroll the list, but the global field in the background doesn't scroll?), but there you have it.
andygaunt Posted June 20, 2002 Posted June 20, 2002 Hi, I use a global field in my solutions. The global is in the database displaying the portal. The calculation in the related database would be something like If (Client Number = interface::global, gBackground, "") So, when the user selects the portal row, it triggers a script that does Set field [Global, client::clientid) So, because the globals are unique to each user, they never get someone elses highlighted records. As you didnt tell us what type of field your tClientNumber was ( I can only assume by the t that it is a text field) HTH
bankofbermuda Posted June 20, 2002 Author Posted June 20, 2002 Andy, Thanks a lot. Works fine. Yes the tClientNumber was a text field. Chris
Recommended Posts
This topic is 8193 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 accountSign in
Already have an account? Sign in here.
Sign In Now