Hello,
Our database has two types of tables:
General tables that hold information pertaining to all our customers.
Tables which hold customer data identified by a customer id field.
Often we need to extract data for a complete system with data of only one or two chosen customers.
When exporting the data we use a where clause limiting the data exported to a certain customer id.
Unfortunatly this is good only for the tables holdig customer data. The general tables without the customer id field are not exported because the where clause naturally couses errors.
That means we have to select tables for general export and then for customer export (with where clause).
It would be nice if there could be an option to use the where clause only if it does not cause errors (if it's relevant), and ignore it otherwise, exporting the whole table.
I realize this solution is only good for my two-type scenario. If a better idea comes to mind then just do it.
Best regards
gad
Our database has two types of tables:
General tables that hold information pertaining to all our customers.
Tables which hold customer data identified by a customer id field.
Often we need to extract data for a complete system with data of only one or two chosen customers.
When exporting the data we use a where clause limiting the data exported to a certain customer id.
Unfortunatly this is good only for the tables holdig customer data. The general tables without the customer id field are not exported because the where clause naturally couses errors.
That means we have to select tables for general export and then for customer export (with where clause).
It would be nice if there could be an option to use the where clause only if it does not cause errors (if it's relevant), and ignore it otherwise, exporting the whole table.
I realize this solution is only good for my two-type scenario. If a better idea comes to mind then just do it.
Best regards
gad
