I have a database which is split between front end and back end with the
front end being local on each computer (3 of them). However, when each user
creates a new query it is stored on the front end user. Is there a way to
store these on the back end so everyone can see them.
Is there any limitation to have just one front end application on the
network that all 3 uses can access via a shortcut on the desktop.
Thanks
Craig
Stefan Hoffmann - 23 Jan 2007 16:19 GMT
hi Craig,
> I have a database which is split between front end and back end with the
> front end being local on each computer (3 of them). However, when each user
> creates a new query it is stored on the front end user. Is there a way to
> store these on the back end so everyone can see them.
Open the backend with DBEngine, this gives you a DAO.Database object.
Then you can use its QueryDefs collection to create a new query and copy
the local QueryDef.
or
Create a table in your backend storing the SQLs. The users then can push
their queries to that table or pull others. Also use the local QueryDefs.
> Is there any limitation to have just one front end application on the
> network that all 3 uses can access via a shortcut on the desktop.
Speed, locking issues, database corruption to name a few.
mfG
--> stefan <--
Tony Toews - 24 Jan 2007 18:32 GMT
>I have a database which is split between front end and back end with the
>front end being local on each computer (3 of them). However, when each user
>creates a new query it is stored on the front end user. Is there a way to
>store these on the back end so everyone can see them.
I would suggest creating another MDB on the server linked to the
backend. Then let the users create queries in that MDB. Note that
they won't be able to do any updates to objects such as queries in
that MDB until the other users have exited that MDB.
>Is there any limitation to have just one front end application on the
>network that all 3 uses can access via a shortcut on the desktop.
Yes, that is very vulnerable to corruptions and makes updating of the
FE more difficult. Although three users isn't too bad.
If you wanted to go though the effort consider using the free Auto FE
Updater utility at http://www.granite.ab.ca/access/autofe.htm at my
website to keep the FE on each PC up to date.
Tony

Signature
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm