Thanks to everyone who helped me on my last question. I've got the
table up and running and have even been able to get file numbers to
match up. The auto increment is working fine for now.

Now I have an issue. Multiple people will have access to this database
and I want to avoid unintentional and intentional damage. I am working
on the auxiliary password to prevent deletion of records.

When an entry in the table is created I would like a date stamp that
cannot be edited at all or only by the highest level user. I would
also like a field showing the last time the table entry was edited.

eventually, I would like to show the last 10 or so users who accessed
the table whether or not it was edited.

if this is getting into the "pay me for my services" realm let me
know.

thanks again.

j.

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote:

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote:

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote:

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote:

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote:

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote:

You might want to check out our AutoArchive product which can do most of
what you need in a slightly different way. It can track changes at a
very granular level and archive the data as it was before the change,
mark the change with the user who did it, etc. It is also capable of
tracking deletes if you set it up for that. It doesn't directly STOP the
changes but by providing an audit trail it lets you see what is
happening and how. You can find it on our product page (Link in my
signature)

I would strongly encourage you to reconsider autoincrement keys if that
is what you are using ai for. Check out the database basics paper on our
paradox resources page for more on why but they are particularly
problematic if you are linking any tables.

You can control some deletes, etc. from paradox based on passwords and
permissions you set but they can be broken and it can get complicated to
manage multiple levels across multiple tables and various users,
permissions and systems. You may also want ot check out our Security
Guard product to help you there. You can learn something about
permissions and passwording from the documentation (free to download)
anyway and you might find that helpful.

HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

spyregyre (AT) gmail (DOT) com wrote: