Why are copies of MDE FE's considered best Access 2002 practice?

[Guest]

"For sure, the fact that you like to press on these issues

shows very much that you do in fact want answers, and
you obviously like getting to the bottom of things!.
This is good!...not bad!"

Albert, you have described me to a T.

I want to thank all of you for putting up with my
questions. I am learning a lot from your responses.

One of those is the importance of reducing network
traffic. Now I have had a lot of experience with network
use because I do use MS Word, MS-Excel, and even MS
Access over a network routinely. While my Word, Excel
and Access are on my PC, my files are all on the network
directory allocated to me for what I work on. And I use
it because that directory and other user directories are
backed up nightly.

At work, I do not experience much delay over our WAN, but
at home, when I work over the cable company's line using
a VPN, I get a lot of slowdown. Actually, for
development of my application, when I work at home, I
generally copy both front and back ends to my computer,
work on them, and then copy the front end back to the
network drive when I have completed what I am going to do
at home.

Incidentally, I am now comfortable with the idea of
having individual front ends for each client pc, because
of yours and other suggestions that I do version
validation via the back end to weed out outdated versions
of the software. This approach is highly validatable and
I can easily sell it to our regulatory folk. The single
centralized fe will be replaced with the distributed fe's
with the next release of this application.

sjl

 

[Stephen J. Levine MD]

The only time I have run into database corruption was
during development, when I inadvertently changed a form
into a pivot table. The corruption was not reparable but
I did salvage the app, which was fortunately in its very
early stages.

I have since made sure to set the pivot table view
property to each form to No.

sjl

 

[John Vinson]

John

You hit the nail on the head. Validation is of software
functionality. And its reliability, particularly where
it is involved in process control.

I would really like to learn more about what you know of
validation in the pharmaceutical industry if you would be
willing to share offline. I have a lot of questions.

sjl

Well, my experience is over ten years out of date (I left Warner
Lambert, now part of Pfizer, in 1992) and haven't had to deal with
cynical data management (oops... *clinical*) since then. I would be
willing to chat (at jvinson <at> wysardofinfo <dot> com) but probably
don't have any concrete help for you on the subject!

 

[Tony Toews]

I would really like to learn more about what you know of
validation in the pharmaceutical industry if you would be
willing to share offline. I have a lot of questions.

No, no, no. Please start a new thread. While strictly speaking this
might be off topic for Access this is certainly software related so
that's close enough as far as I'm concerned. It'll be quite
interesting to see how different or how close, the things I do without
even realizing it are to one particular industry standard.

And for once I'm going to throw my weight as an MVP around and declare
that this topic be consider On Topic for this newsgroup. <smile>

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

 

[John Vinson]

And for once I'm going to throw my weight as an MVP around and declare
that this topic be consider On Topic for this newsgroup. <smile>

Tony

ah, but is this opinion validated in accord with FDA rules? <bg>

Good idea. Let's get some other experience into the thread!