>If you store alerts in the db, you should set uo a separate table for
>alerts say
>
>AlertID PK
>AlertUserID FK references(User, UserID)
Thanks for your suggestion. A separate table seems like a good idea. The
AlertID field would be a PK (Primary Key). What kind of key is FK? (I'm
using Access, would that be a "link" in Access?).
In this scenario, when I populate the "Alerts" table with CF, how would the
AlertUserID field be populated? Should I use INSERT to put that info there,
or should it come from the original USERS table using the built-in
relationship?
Roberto
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
