Looking for a better solution....

[brad2610]

I have a inventory database used by 15 different clients. Each logs in with there given login and pass. In my privleages I set a calculation to allow them to only see the data that is associated with them. This is done by setting the records access to limited. I use the calculation:

(Records can be viewed when Client="Ultra") (ultra being one of my clients names)

Every record has been tagged with a client name in order to make this work. This was the simplest way i could make this work and seems easy to maintain. My only conern is that this slows the database down as this calculation must be preformed on every lookup.

Does anyone have any suggestions on how this might be done with less intensive provessor use?

Thanks

Brad

[Brian C]

I am guessing that all of your clients are logging into the same database served from the same server.

Im not sure if this is practical, but you could try using a self relationship from a global field to the client name field. You could store the client name in the global field to make the relationship work. By using "go to related records" you could have just the set of records for that client be in the found set.

If you place tighter controls on your find processes you could incorporate this approach directly into any find steps that are executed and just make sure that any find will either plug in the current client name automatically from the global field or do a "go to related records" and then do a constrain find on any additional search criteria.

This is not a very elegant approach but given what is being attempted, it might fit your needs.

[Brian C]

I am guessing that all of your clients are logging into the same database served from the same server.

Im not sure if this is practical, but you could try using a self relationship from a global field to the client name field. You could store the client name in the global field to make the relationship work. By using "go to related records" you could have just the set of records for that client be in the found set.

If you place tighter controls on your find processes you could incorporate this approach directly into any find steps that are executed and just make sure that any find will either plug in the current client name automatically from the global field or do a "go to related records" and then do a constrain find on any additional search criteria.

This is not a very elegant approach but given what is being attempted, it might fit your needs.

[Brian C]

I am guessing that all of your clients are logging into the same database served from the same server.

Im not sure if this is practical, but you could try using a self relationship from a global field to the client name field. You could store the client name in the global field to make the relationship work. By using "go to related records" you could have just the set of records for that client be in the found set.

If you place tighter controls on your find processes you could incorporate this approach directly into any find steps that are executed and just make sure that any find will either plug in the current client name automatically from the global field or do a "go to related records" and then do a constrain find on any additional search criteria.

This is not a very elegant approach but given what is being attempted, it might fit your needs.