Access9001
03-26-2010, 09:24 AM
By that I mean I have processes that create tables, processes that extract data, others that export files, and so forth. But there are always issues if someone else is using a given database or file (thereby tying up other processes that either need to access said object for whatever reason).
Is there a general way to avoid such issues? On a modular, macro-level, what is the best way to typically arrange these processes in order to ensure things run smoothly?
Typically I try to separate backend from frontend, but when people use the frontend, it still locks the backend tables, for instance. Or if I need to overwrite/edit/access an Excel file, and someone has it open, there will be problems.
Is there a general way to avoid such issues? On a modular, macro-level, what is the best way to typically arrange these processes in order to ensure things run smoothly?
Typically I try to separate backend from frontend, but when people use the frontend, it still locks the backend tables, for instance. Or if I need to overwrite/edit/access an Excel file, and someone has it open, there will be problems.