How can I retain customized data selected by each users of my ADP application.
With an ADP everything seems parishable unless you keep tables for each users in the shared database, which is a bad idea because I have 1000 users performing many different data requests. I can store limited information on a form but some users want to be able to recall data records they previously retrieved in order to make comparisons.
With an .mdb as my front-end, it can have local tables that can hold information about what the particular use performed or requested in the past. Sometimes the users wants to review what they retrieved in the past though they may not recall how they did it. I can also use local tables to store defaults (profiles) based on the user's activity in the application thus reducing search and process time. Each user's front-end contains a customized profile that follows/adjust to the user and is retained beyond the current session.
I'd appreciate your thoughts on how to do this with an ADP?
Bob
With an ADP everything seems parishable unless you keep tables for each users in the shared database, which is a bad idea because I have 1000 users performing many different data requests. I can store limited information on a form but some users want to be able to recall data records they previously retrieved in order to make comparisons.
With an .mdb as my front-end, it can have local tables that can hold information about what the particular use performed or requested in the past. Sometimes the users wants to review what they retrieved in the past though they may not recall how they did it. I can also use local tables to store defaults (profiles) based on the user's activity in the application thus reducing search and process time. Each user's front-end contains a customized profile that follows/adjust to the user and is retained beyond the current session.
I'd appreciate your thoughts on how to do this with an ADP?
Bob