Thx to LoisC, I figured out how to get my database to force "new" users to add a record, where subsequent visits would "not" get the Add Record prompt, :-)
However, the only way I got it to work was by changing the $db_key from the original AlumniID (counter) to the UserID.
The problem (or is it?) is that a few of my records use the same UserID, :-0. I've cautioned my alumni to "not" update any thing other then their entry, but I understand how they'd want to update their sibling off-line folks to the database, "understanding", they are ultimately responsible for updates of those siblings.
The .cfg states, "The column name for the database key. Can be any column, but it must be unique! You can't have two records with the same key value! So ... if I change to User-Id, I have multiple records with the same key value -- if I leave it as the AlumniID (counter), I can't get it force the Add AND not stop the subsequent visits from getting the Add form, :-0.
Suggestion, Comments?
JR
However, the only way I got it to work was by changing the $db_key from the original AlumniID (counter) to the UserID.
The problem (or is it?) is that a few of my records use the same UserID, :-0. I've cautioned my alumni to "not" update any thing other then their entry, but I understand how they'd want to update their sibling off-line folks to the database, "understanding", they are ultimately responsible for updates of those siblings.
The .cfg states, "The column name for the database key. Can be any column, but it must be unique! You can't have two records with the same key value! So ... if I change to User-Id, I have multiple records with the same key value -- if I leave it as the AlumniID (counter), I can't get it force the Add AND not stop the subsequent visits from getting the Add form, :-0.
Suggestion, Comments?
JR
Discussion: $db_key