i am sure most of us Access users are familiar with Access crashing/going corrupt. especially it is the UI form or the VBA code that goes bad. though we can't entirely do away with this issue we can certainly minimize it to some extent.
-one solution that is suggested and also as i have experienced is to 'Split' the database. Splitting simply refers to maintain a separate database with all the tables required and in turn linking these tables [back-end] with other database having the required UI Forms and the VBA code [front-end].
-we can further have multiple copies of front-end database for each user too.
this helps in minimizing crashes as it avoids loading of every form and code in to the memory from same location for each user.
-one solution that is suggested and also as i have experienced is to 'Split' the database. Splitting simply refers to maintain a separate database with all the tables required and in turn linking these tables [back-end] with other database having the required UI Forms and the VBA code [front-end].
-we can further have multiple copies of front-end database for each user too.
this helps in minimizing crashes as it avoids loading of every form and code in to the memory from same location for each user.
No comments:
Post a Comment