Member Avatar for server_crash

Take this situation: A Hospital Database containing information on over 800 employees. Which database software would you use? Is Access just as good as mysql?

  • 3 Contributors
  • 4 Replies
  • 199 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by freesoft_2000

Dani AI

Generated

— short answer: it depends, like already hinted. For a hospital roster of ~800 people Access can work when the number of simultaneous users is low and the application is designed as a split front-end/back-end. For heavier concurrent use, strict uptime, audit/logging or stronger security needs, a client/server engine (MySQL, SQL Server, etc.) is a safer long‑term choice.

What to check now (focus on facts you can verify):

  • Confirm how many users actually have the back-end open by asking the Novell/NetWare admin to list open file handles (server “open files” / connection viewer). That will show real connections, not guesses.

  • Reproduce the “changes only register on second try” with two test machines to see whether it’s client-side UI caching or a server sync/lock issue. Look for missing form requery/refresh calls or for delayed write/commit behavior. A quick form-level test in Access:

    ' after saving a record, force the UI to show current data
Me.Refresh
Me.Requery

  • Check for interfering factors: antivirus scanning, client or server caching, Novell workspace settings, or a single shared front-end (everyone must have a local copy of the front-end).

Practical fixes you can apply today:

  • Split front-end/back-end; give every user a local front-end copy and share only the data file.
  • Compact & repair the backend regularly and ensure backups are in place.
  • Enable record-level locking in Access (rather than page-level) and avoid keeping long transactions open.
  • If the environment must support many concurrent users or needs strong auditing/encryption, plan migration to a server RDBMS — that removes file-share lock limitations and gives better tools for monitoring and backups.

As suggested, implementation matters—if you can tell which Novell server/version is in use and how users connect, more specific diagnostic commands and settings can be suggested.

Recommended Answers

All 4 Replies

Member Avatar for Kate Albany

server_crash,

It depends on more than just the number of rows you are going to store, like the complexity of the querys, the number of concurrent users the DB must service, performance metrics etc .........

Having said that, I would say that a small DB with < a few thousand rows, and with a small number of concurrent users, that Access would be just fine in this case.

Kate

Member Avatar for freesoft_2000

Hi everyone,

I would use my own implementation - - If you know what i mean - wink

But on the serious side i yhink that access would better suit your needs

Richard West

Member Avatar for server_crash

Well, this isn't my DB. It's the hospitals that I work at. I'm wondering since access is limited to only 5 connections if that could be the cause to some of the problems it's having, or if it could be the access "programmer"(as they call him). The database is not registering changes untill the second time, but I'm not sure how many people other than me have access to it. It is on a novell workspace, so that is questionable. I wish there was a way I could find out how many connections are actually made to it.

Member Avatar for freesoft_2000

Hi everyone,

I wish there was a way I could find out how many connections are actually made to it.

I am not sure about this but i think it would equire you using some winapi classes.

Sorry i could not be of much help

Richard West

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.