Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Also see <a href="http://www.granite.ab.ca/access/corruptmdbs.htm" rel="nofollow noreferrer">Corrupt Microsoft Access MDBs FAQ</a> Which I've compiled over the years based on newsgroup postings and predates Allen's page. That said my clients have had very few corruptions over the years and have never lost data nor had to restore from backup.</p> <p>I'm not sure what "write your program correcly" means in this context. I've read a few postings indicating this but it's more the implementation aspects. As Albert has pointed out you have to split the database and give each user their own copy of the FE MDB/MDE. You can't access a backend MDB over a wireless network card as they are too unstable. Same with a WAN unless the WAN is very fast/wide and very stable. We then suggest upszing to SQL Server or using Terminal Services/Citrix.</p> <p>I have several clients running 20 to 25 users all day long into the system. One MDB has 120 tables while another has 160 tables. A few tables have over 600,000 to 800,000 records. The one client had 4 or 5 corruptions in five or seven years. We figured out the cause of all but two of those. And they were hardware related in one way or another. At least one of these apps should've been upsized to SQL Server. However that was cancelled on me by a Dilbert's PHB (Pointy Haired Boss).</p>
    singulars
    1. This table or related slice is empty.
    1. POProper way to program a Microsoft Access Backend Database in a Multiuser Environment
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USonedaywhen
    1. USTony Toews
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHere's what I mean by "Write your program correctly." I have broad personal experience with corruption in Access databases. It is my opinion that an interrupted write is a poor excuse for a database catastrophically crashing. When I explain this to your MVP friends, they tell me that I am incompetent and ignorant, and that I just don't know how to program it correctly. See http://stackoverflow.com/questions/1115385/microsoft-access-2007-power-users/1115424#1115424
      singulars
      1. PO
      1. USRobert Harvey
    2. COWhereas I have very little personal experience with corruptions as I've seen so little of them. However I've read almost all of the Usenet and Microsoft NNTP newsgroup postings on this topic. What do you mean by "interrupted write?" Hardware failure? User hitting the power switch? Or something in your code? I agree that SQL Server and similar are a better solution in many respects. However frequently IT has a strangle hold on such. And they're more work to setup and administor.
      singulars
      1. PO
      1. USTony Toews
    3. COAh, ok, please note that David Fenton is not an MVP. Although for the most part he does post good answers. At times the attitude in his postings do reflect his New York heritage. And we've had this discussion in the newsgroups a while back so he knows where I'm coming from on this issue. David should explain in greater detail what he means. Some of it will be the obvious things such as not pulling down forms based on queries with thousands of records.
      singulars
      1. PO
      1. USTony Toews
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload