Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can tell you from painful experience that Jet 3/3.5 was not reliable. I saw it crash frequently under light load and when there were crashes you risked data corruption. It used to be extremely sensitive to any power problems, any client crashing against it (even the UI linked to the mdb), and any LAN problems. More recent versions of Jet might be better but switching to Sql Server is clearly the way to go in my opinion for anything other than trivial data entry with a small number of users. Sql Express is free and you don't really lose anything, especially if you're UI is in .Net, rather than Access.</p> <p>EDIT: Microsoft doesn't think you should rely on Jet 4 either.</p> <p>from: <a href="http://support.microsoft.com/kb/303528" rel="nofollow noreferrer">http://support.microsoft.com/kb/303528</a></p> <p>Microsoft Jet is not intended for use with high-stress server applications, high-concurrency server applications, or 24 hours a day, seven days a week server applications. This includes server applications, such as Web applications, commerce applications, transactional applications, and messaging server applications. For these types of applications, the best solution is to switch to a true client/server-based database system, such as Microsoft Data Engine (MSDE) or Microsoft SQL Server. When you use Microsoft Jet in high-stress applications such as Microsoft Internet Information Server (IIS), you may experience any one of the following problems: Database corruption Stability issues, such as IIS crashing or locking up Sudden failure or persistent failure of the driver to connect to a valid database that requires re-starting the IIS service</p>
    singulars
    1. This table or related slice is empty.
    1. POIs MS Access (JET) suitable for multiuser access?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USbglenn
    1. USbglenn
    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. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJet 3 was released with Access 95, the first Access version to incorporated VBA. By general agreement among Access developers, it was the worst version of Access ever released, and was superceded just a year after its release by the much, much better A97 (which many developers still consider the best Access version ever). A97 shipped Jet 3.5, which was rather buggy in its original release. It took a couple of Jet service packs and a couple of patches to make A97 rock-solid. So, perhaps you didn't use A97 long enough to experience the fully patched version.
      singulars
      1. PO
      1. USDavid-W-Fenton
    2. COCommenting on Access and Jet/ACE as it exists today with references to a version of Jet that was superseded over 10 years ago (Jet 4 shipped with A2000 in June 1999), seems to me to demonstrate that you really don't have anything to add to the conversation.
      singulars
      1. PO
      1. USDavid-W-Fenton
    3. COI specifically pointed out that I wasn't commenting on the current Jet version. That the engine had well known problems with data integrity that I experienced first hand in a mature release (3.5 with all the SPs/patches) that is not that long ago is very relevant to the original post. One data corruption problem is enough to sour you on an engine for life. I've never seen a data corruption problem in Sql Server (caused by the engine). While current Jet/ACE might be as solid as Sql Server, I wouldn't bet on it when you have Sql Server Express/Adp projects as a costless alternative.
      singulars
      1. PO
      1. USbglenn
 

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