Happy Friday!
So I've designed a database, but my oh my it's so slow! The purpose of the database is a healthy pregnancy program. I have to load thousands of eligible women into the database so that the employee can then find the women who will be in the program. So basically, the user doesn't have to input a bunch of data about the women in the program; it's all there for her already.
With thousands of records, the database runs so slow because of course it runs through all of the records whenever a query is run, etc. How do I create it so that there is a table for the thousands...most of which are not needed...but when she "chooses" a record of a woman who will participate in the program, that woman's record gets put into a table of "Participants". This way, when I create queries or reports for her, they will only have to be run against the few hundred that she is working with. Any ideas?
OH and FYI...I will likely be splitting this database, so the table with the thousands could be in the BE and the table of "Participants" could be in the front end.
Thank you!!