hi,
i am a (relative) newbie to all this and still haven't added user level security to my (under development) access 2000 database but that is definitely something that's going to be done down the pike; one of my users is asking for record level security. i heard there've contentions among users claiming 'the other guy' did this or did that to a record in a table in a database; although my user's not sophisticated enough to invoke the term 'record level' security, my guess is they would if they could.
on one level, i suppose the 'quick and dirty' way is to create two copies of the same database and prevent the other user from accessing the other's database, and at some point go ahead and merge the corresponding tables in a third database. but if there were something slicker to allow more than one user to access the same table within the same database while prevent his cohorts from ever modifying a record in the table that 'belonged' to that user, then that'd be kind of cool. i don't think that that can be done, and that ms access 2000 can let you drill down only as far down as to table level security. is this in fact a native capability of ms access 2000's?
i am a (relative) newbie to all this and still haven't added user level security to my (under development) access 2000 database but that is definitely something that's going to be done down the pike; one of my users is asking for record level security. i heard there've contentions among users claiming 'the other guy' did this or did that to a record in a table in a database; although my user's not sophisticated enough to invoke the term 'record level' security, my guess is they would if they could.
on one level, i suppose the 'quick and dirty' way is to create two copies of the same database and prevent the other user from accessing the other's database, and at some point go ahead and merge the corresponding tables in a third database. but if there were something slicker to allow more than one user to access the same table within the same database while prevent his cohorts from ever modifying a record in the table that 'belonged' to that user, then that'd be kind of cool. i don't think that that can be done, and that ms access 2000 can let you drill down only as far down as to table level security. is this in fact a native capability of ms access 2000's?