We have an existing database that we have been using for years and has become the backbone of our business.
When the database was developed, all company information (name, address ,telephone, etc etc) was manually included in every report, letter, etc.
The powers to be now want all this information to be editable via a 'company information' form. This form needs to allow them to change all company information and any other fields used throughout the database that have default values (past due messages, invoice notes, etc).
My initial thought was to create a 'company info' table with a field for every value they want to be able to edit. This would also require linking this table to every other table in the database via a set. All existing reports and letters would have to be recreated referencing the new set. This seems like way too much work and too much overhead on system resources.
My other thought is to create a 'company information' form and set an 'onsave' event that sets all of the editable fields to a global variable. I could set these variables globally on startup and change the values when a field is changed on the company information form. All reports and letters would have to be edited referencing the new variables but at least new sets would not have to be created.
Am I overlooking anything in my 'variable' option?
Thanks for the help
When the database was developed, all company information (name, address ,telephone, etc etc) was manually included in every report, letter, etc.
The powers to be now want all this information to be editable via a 'company information' form. This form needs to allow them to change all company information and any other fields used throughout the database that have default values (past due messages, invoice notes, etc).
My initial thought was to create a 'company info' table with a field for every value they want to be able to edit. This would also require linking this table to every other table in the database via a set. All existing reports and letters would have to be recreated referencing the new set. This seems like way too much work and too much overhead on system resources.
My other thought is to create a 'company information' form and set an 'onsave' event that sets all of the editable fields to a global variable. I could set these variables globally on startup and change the values when a field is changed on the company information form. All reports and letters would have to be edited referencing the new variables but at least new sets would not have to be created.
Am I overlooking anything in my 'variable' option?
Thanks for the help
Comment