ontopofmalvern
Registered User.
- Local time
- Today, 20:51
- Joined
- Mar 24, 2017
- Messages
- 64
Hi
Firstly apolgies for the rambly-ness of this post - I not really after solutions just general pointers and links to materail that could help.
I have (by my standards) a complex database which is split between a FE and BE, it has about 30 users who all have a copy of front end and access the BE on network drive. The FE is becoming a little ill - it is bloating and will no longer compact and repair. I have a long list of thngs I should do to it to make it more comfortable and plan some major surgery. 2 things I would be most grateful for further general pointer on before I go in.
Firstly my front end has a small number of small tables - I think this might count as a cardinal sin (?) - all but one of these tables stores tempoary calculated data used for reports and charts . There is also one very small table which stores some user defaults. What is the general advice on good practice for these tables? The data ones could go in back end, be emptied on close or even dropped on close (then recreated as needed). For the defaults is there a standard way of having user defaults (currently for each user it is just 2 interger fields so it is tiny).
Any pointers on how to deal with FE 'bloat' would also be great - it used to be about 10mb but is now 50mb and rising (I do have older versions to roll back to if necessary but I'd like to fix this version). I read somewhere that these problems can be the result of file coruption and can be solved by starting again and copying everyhting accross (no small task) - does that make sense or is it a fools errand?
Many thanks for any help - love this forum it has saved my life several time before (okay not my life as such...)
Richard
Firstly apolgies for the rambly-ness of this post - I not really after solutions just general pointers and links to materail that could help.
I have (by my standards) a complex database which is split between a FE and BE, it has about 30 users who all have a copy of front end and access the BE on network drive. The FE is becoming a little ill - it is bloating and will no longer compact and repair. I have a long list of thngs I should do to it to make it more comfortable and plan some major surgery. 2 things I would be most grateful for further general pointer on before I go in.
Firstly my front end has a small number of small tables - I think this might count as a cardinal sin (?) - all but one of these tables stores tempoary calculated data used for reports and charts . There is also one very small table which stores some user defaults. What is the general advice on good practice for these tables? The data ones could go in back end, be emptied on close or even dropped on close (then recreated as needed). For the defaults is there a standard way of having user defaults (currently for each user it is just 2 interger fields so it is tiny).
Any pointers on how to deal with FE 'bloat' would also be great - it used to be about 10mb but is now 50mb and rising (I do have older versions to roll back to if necessary but I'd like to fix this version). I read somewhere that these problems can be the result of file coruption and can be solved by starting again and copying everyhting accross (no small task) - does that make sense or is it a fools errand?
Many thanks for any help - love this forum it has saved my life several time before (okay not my life as such...)
Richard