A Jet 4 backend Access database is good for most small physician offices that are small enough to still be able to use a Windows XP P2P network (i.e. objective limitation of 10 for WinXP to the backend AC computer, and the subjective limitation of up to ~20 for a Jet 4 backend database).
Other than the fact that a Jet 4 backend means that chart graphics are very limited, what specifically do you have against a Jet 4 backend? It's a wonderful, inexpensive platform onto which one can develop an excellent EMR, with a rich VBA programming environment. What else does an SQL have that you want? For example, is your AC database that slow? It shouldn't be, and if it is, it's usually because of other factors...
Be careful with what you wish for, as it's going to cost you both in software and hardware resources!
AL
Last edited by alborg; 07/12/2008 12:21 AM.