I have been given the task of stream-ling our database. Previously someone created a range of queries, and then forms which open these queries through command buttons.
For example -
Query the main table for a country - Albania (for example)
Then query a query - Query Albania - for contact type - say expert
In each individual country there was 20 different contact types, with each of these queried. So for one country alone, you have the initial filter of country, and then 20 additional queries.
These were then opened via command buttons on forms.
As you can imagine, when you times that by the amount of countries you are looking at thousands of queries in total. This has obviously led to the database being extremely cumbersome. The original point to this method was that within a few clicks you could have isolated - the country and type of contact incredibly quickly... Is there another way of redesigning the database to make this possible?
Many thanks
For example -
Query the main table for a country - Albania (for example)
Then query a query - Query Albania - for contact type - say expert
In each individual country there was 20 different contact types, with each of these queried. So for one country alone, you have the initial filter of country, and then 20 additional queries.
These were then opened via command buttons on forms.
As you can imagine, when you times that by the amount of countries you are looking at thousands of queries in total. This has obviously led to the database being extremely cumbersome. The original point to this method was that within a few clicks you could have isolated - the country and type of contact incredibly quickly... Is there another way of redesigning the database to make this possible?
Many thanks