SmartbizAustralia said:
Splitting the data/BE does help prevent corruption so what reason is
there for this separation except to save 10 seconds on loading?
Well, I'm not sure sure you'd save that 10 seconds. Leaving an FE MDB/MDE means that
you'd have to fetch various objects such as queries, forms, reports and modules from
the server as required. Thus leading to a sluggish app. That said one of my clients
chose to do this on a Citrix environment and it wasn't too bad. However I designed
the Auto FE Updater to ensure each user on the Citrix server had their own copy of
the FE MDE anyhow.
Also you'd only need to copy down the FE when there's a new version on the server.
Especailly with Access 2002/2007 versions, is this extra complication
going to help.
Yes.
The main reason I am against this is that we have three enviroments
for each system, Developement, Testing and Production. So the front
end always checks and updates it's links to the BE in the same
directory.
This makes moving the updates to testing and then to production very
simple.
You could put some code in to handle this situation. For example designate some
workstations as development, test or other. Then ensure the tables are linked to the
appropriate backend depending on that designation.
I saw some articles regarding errors with people updating filters, but
is this still the main reason why you would want to put the FE on the
user's pcs?
Sharing an Access FE MDB/MDE can cause corruptions in the FE MDB/MDE. And downright
wierdness. You also can't update the FE MDB/MDE to a new version until everyone is
out of it.
Tony
--
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
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/