Regarding this post, got me thinking.
Re: How to query a backEnd database from a frontend database with a Sql script
http://www.access-programmers.co.uk/forums/showthread.php?t=287797
Can this technique be used to create an equivalent of a "linked table" for queries. I have FE/BE and there are some queries that I would like to either be standardized or customized and protected from FE version updates. If these UD/UAQ (User Defined/User Altered Queries) were stored in a separate file, then I wouldn't have to worry about them being wiped out or replaced with a more generic version.
If I go this way, is there a performance issue per CJ London
Re: How to query a backEnd database from a frontend database with a Sql script
http://www.access-programmers.co.uk/forums/showthread.php?t=287797
Can this technique be used to create an equivalent of a "linked table" for queries. I have FE/BE and there are some queries that I would like to either be standardized or customized and protected from FE version updates. If these UD/UAQ (User Defined/User Altered Queries) were stored in a separate file, then I wouldn't have to worry about them being wiped out or replaced with a more generic version.
If I go this way, is there a performance issue per CJ London
or some other unintended issue that may arise from this novel approach?benefit is the back end is open persistently so lower time overhead on getting the records, whereas your method isn't, although fine for occasional access to other data.