Louis,
Yes, there will be many ID's associated with each record in 'tickets.db'. So, the information probably does need to be stored in the field in tickets.db.
What I have is a field in ticket.db in which ID's from work.db can be entered into it. xxxx,xxxx,xxxx Is an example for 3 ID's. Then on the record display from tickets.pl it breaks apart each of the ID's so they are clickable.
So, I need the add_record_success in work.pl to add the ID that was just added to work.db to the field in tickets.db for the associed record with ID (in tickets.db) to the number entered into field 'Ticket' on the add form in work.pl.
Does this make sense?
Yes, there will be many ID's associated with each record in 'tickets.db'. So, the information probably does need to be stored in the field in tickets.db.
What I have is a field in ticket.db in which ID's from work.db can be entered into it. xxxx,xxxx,xxxx Is an example for 3 ID's. Then on the record display from tickets.pl it breaks apart each of the ID's so they are clickable.
So, I need the add_record_success in work.pl to add the ID that was just added to work.db to the field in tickets.db for the associed record with ID (in tickets.db) to the number entered into field 'Ticket' on the add form in work.pl.
Does this make sense?