When my users touch a record, it would be useful for our process if the data (under certain specific conditions) marked itself (there already exist Yes/No fields for each user to mark manually, and the database is split, so that each user has his own version of the front end). So I'm thinking that something vaguely like a log-in would allow each user to identify himself at start-up (we just use initials), and my code could access that identity when I needed it. I realize this is a simple concept, but for me, it's complicated by the odd data structure, where each record contains what amounts to 3 instances of a sub-record, but it's not nicely structured: each instance has the same set of fields, the names of which are just appended with "(2)" and "(3)", and I'd be setting a single tag in one of the three instances. Ugly.
Anyway, I'm thinking that I'm going to have to use case statements based on the specified identity (yes? no? something better?). Should I store this identity in some kind of global variable? In a data table that mimics the existing set of user tags?
Since more than one user can have a record marked for his own purposes, I don't want to just set a tag in the set of identities and simply plop those values into each record.
Alternatively, maybe it's time for me to make a major shift in the structure and array these instances, but I've never worked with VB's arrays.
Thanks for any advice/ideas.
Anyway, I'm thinking that I'm going to have to use case statements based on the specified identity (yes? no? something better?). Should I store this identity in some kind of global variable? In a data table that mimics the existing set of user tags?
Since more than one user can have a record marked for his own purposes, I don't want to just set a tag in the set of identities and simply plop those values into each record.
Alternatively, maybe it's time for me to make a major shift in the structure and array these instances, but I've never worked with VB's arrays.
Thanks for any advice/ideas.