This is really just a question of principle;
Is it really necessary to locate a backend and refresh the links each time a front end is opened?
I've seen code to do this in a few places now, and wonder how essential it is.
By my un-educated understanding, Access (97) uses Linked tables in order to avoid the necessity of re-creating ODBC connections each time they are needed. These links are refreshed each time the backend tables are opened.
The only errors I can think of are the backend missing or being corrupted, in which case a DBA is best placed, and may be the only person authorised, to resolve this.
So all that's needed in these cases is some basic error trapping, to alert the user to notify a DBA.
The only reason I can think for using code to refresh the links may be performance based. ??
Could anyone point out if my logic is flawed somewhere.
I'm not trying to be complacent, just efficient.
Remy Still new to DB's and enjoying learning day by day
Is it really necessary to locate a backend and refresh the links each time a front end is opened?
I've seen code to do this in a few places now, and wonder how essential it is.
By my un-educated understanding, Access (97) uses Linked tables in order to avoid the necessity of re-creating ODBC connections each time they are needed. These links are refreshed each time the backend tables are opened.
The only errors I can think of are the backend missing or being corrupted, in which case a DBA is best placed, and may be the only person authorised, to resolve this.
So all that's needed in these cases is some basic error trapping, to alert the user to notify a DBA.
The only reason I can think for using code to refresh the links may be performance based. ??
Could anyone point out if my logic is flawed somewhere.
I'm not trying to be complacent, just efficient.
Remy Still new to DB's and enjoying learning day by day