[AccessD] Mac users corrupt Access database (was: Memo field corruption)

[Jim Dettman]

 It's not the fault of the Mac's, it's the network.
 
 The Mac's are just pushing the network and it would be the same problem if
Windows machine did the same.  The fault lies in the network.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Gustav Brock
Sent: Wednesday, February 20, 2019 3:48 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Mac users corrupt Access database (was: Memo field
corruption)

Hi Susan et al

This caught my attention, for an obvious reason:

MS Access keeps crashing on Network cause of Mac users

https://answers.microsoft.com/en-us/msoffice/forum/all/ms-access-keeps-crash
ing-on-network-cause-of-mac/d9b622ea-eebe-4548-955c-2a923d11b815?tm=15506517
26677

A bit surprising if Macs still should be able to cause this trouble.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces at databaseadvisors.com> På vegne af Gustav Brock
Sendt: 26. januar 2019 18:30
Til: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Emne: Re: [AccessD] Memo field corruption

Hi Susan

Ah, ten years back!

#3: Don't use memo fields
This is probably too harsh - I haven't met, nor heard of, a single issue
since that article.

#4: Don't store picture files
This, however, is still valid, except if pictures are few and small. But the
issue is more related to bloating the backend rather than corrupting it.

#6: Be careful with wireless networks (WiFi) This should be rephrased to:
Never connect via wireless networks (WiFi) I've heard of numerous troubles
when connecting via WiFi. It may work well (as stated) with R/O access, but
how many backends are attached for R/O only?

#8: Don't put Mac and Windows users on the same network This is not valid
anymore, or should at least be turned into a general note, that devices that
can cause a heavy load on the network should be isolated from the traffic
between Access frontends and their backends.

Impressive list of comments, by the way. 

/gustav



________________________________________
Fra: AccessD <accessd-bounces at databaseadvisors.com> på vegne af Susan
Harkins <ssharkins at gmail.com>
Sendt: 26. januar 2019 17:55
Til: 'Access Developers discussion and problem solving'
Emne: Re: [AccessD] Memo field corruption

Gustav, a question from a reader prompted my question -- remember that
article we wrote a long time ago?

https://www.techrepublic.com/blog/10-things/10-ways-to-prevent-access-databa
se-corruption/

It's so old -- I wonder if the memo issue hasn't improved?

Susan H.


That's what I have done - for pictures. I even used a second backend to hold
this single table to not bloat the main backend.

/gustav


I think a lot of "expert" database developers suggest keeping the memo field
in a separate table using a 1:1 or 1:n relationship -- just in case.

Susan H.


I always include memo fields in the same table.  I haven't heard of what you
described - have you seen that done somewhere?

Dan


When you include a memo field, do you include it in the table or do you
relate to a second table that stores just the memo field?

Susan H. 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com