My DB has grown to be fairly large (23 forms/subforms & 55 tables). The majority of the tables contain lists that I use to populate comboboxes.
I recently discovered and dove into the world of split databases. The split is great (backend saved on server, frontend .mde saved on local computers, & code that keeps the connection open to improve performance).
However, one of my employees works remotely from home. She continues to complain that the performance of the DB has decreased to an irritatingly slow level. Specifically, when she tries to use comboboxes.
Does hard coding the choices in the combobox reduce resources? I'd simply have to re-deploy the frontend app if/when I add/change choices.
Or, should I import the lookup tables from my backend into my frontend instead of linking them?
I'm open to any other suggestions! Thanks in advance.
I recently discovered and dove into the world of split databases. The split is great (backend saved on server, frontend .mde saved on local computers, & code that keeps the connection open to improve performance).
However, one of my employees works remotely from home. She continues to complain that the performance of the DB has decreased to an irritatingly slow level. Specifically, when she tries to use comboboxes.
Does hard coding the choices in the combobox reduce resources? I'd simply have to re-deploy the frontend app if/when I add/change choices.
Or, should I import the lookup tables from my backend into my frontend instead of linking them?
I'm open to any other suggestions! Thanks in advance.