Liz
Do you have the forms record locking set to Edited Record? That's the safest way to do it in a multi-user application. I haven't had any data corruption in years. But then maybe it's just a solid LAN that makes my life simpler.
Regards,
Bill
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Liz Ravenwood
Sent: Thursday, January 30, 2014 9:21 AM
To: 'MS_Access_Professionals@yahoogroups.com'
Subject: RE: [MS_AccessPros] RE: Access on LAN vs. WAN
Ah –tis just the basic recommended. Split out, front end for each user linking to the back end. A development copy for my testing, and then I deploy to an area where the user runs a script to take the latest. It's what I got as recommended from this wonderful group.
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Bill Mosca
Sent: Thursday, January 30, 2014 10:06 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] RE: Access on LAN vs. WAN
No attachments, Liz. You'll have to upload the file.
Regards,
Bill
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Liz Ravenwood
Sent: Thursday, January 30, 2014 8:12 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] RE: Access on LAN vs. WAN
Thanks all. I do have a split system. It's just that I get more corruption than I'd like (any corruption is too much). It's the Chinese/kanji style that does the reserved error – and the search key not found in any index sort of thing.
I don't know if you can get this attachment, but this is my configuration.
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Tony Meece
Sent: Thursday, January 30, 2014 8:55 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] RE: Access on LAN vs. WAN
Greetings Liz,
Have worked with Networked Access DB's for 18 years. Loosing connection due to and Network Issue can corrupt your DB, especially if using the Single DB model. If you split the data from the Code, the likelihood of corruption is diminished substantially. Distribute your Code modules to each client, if possible.
Further, if you design using Static Copies of the data unless performing changes (use short Transactions) , the DB becomes very stable. It requires more work when designing, but the payoff is worth it.
That said, Access has gone thru a number of updates which has improved the ability to recover from a lost connection. The DB can 'crash' and recover. But my rule of thumb from the 'early days' is ALWAYS keep a backup.
Good luck,
7ony
On Thursday, January 30, 2014 10:34 AM, "wrmosca@comcast.net<mailto:wrmosca@comcast.net>" <wrmosca@comcast.net<mailto:wrmosca@comcast.net>> wrote:
Hi Liz
LANs are usually pretty good because of the better connection. WANs can be tricky if the connection is not solid. This is the best argument for a split DB with the front end local. But all this is just from what I've picked up second-hand.
---In MS_Access_Professionals@yahoogroups.com<mailto:MS_Access_Professionals@yahoogroups.com>, <liz_ravenwood@beaerospace.com<mailto:liz_ravenwood@beaerospace.com>> wrote:
Anyone have any information regarding semi-technical pros and cons on running Access in LAN vs. WAN and particularly the issues or non-issues with running it from Citrix?
Doing a little homework here…
Respectfully,
Liz Ravenwood
Programmer / Analyst
B/E Aerospace | Super First Class Environments
1851 S Pantano Road | Tucson, Arizona 85710
Office +1.520.239.4808 |
beaerospace.com
Passion to Innovate. Power to Deliver
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
[Non-text portions of this message have been removed]
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (8) |
Tidak ada komentar:
Posting Komentar