D
David P. Lurie
Acccess 2003 Developer Extensions
An electronic medical records system for my office is being developed, using
Jet for the initial prototype. The eventual production version may need to
use a different backend.
The number of users at any time will be light, less than five, but the
database size will eventually grow past 2GB. Data once entered would rarely,
if ever be changed, but old data needs to be available for queries.
Archiving records yearly to new Jet or MSDE databases would keep the size
within limits; I was planning to use UNION queries to concurrently retrieve
data from archived years. The office server runs SCO OpenServer 5.0.7, such
that it can't run IIS, but the number of users is low enough that IIS on my
XP system could host data access pages.
Replication (or possibly just one or two local and remote(LAN) scheduled
database backups per day) is needed to ensure system availability in the
event of hardware failure. Remote access via VPN is needed for both myself
and my transcriptionist. That would require MSDE or postgresql rather than
Jet, unless data access pages are used.
I've gotten client-server functionality from access to postgresql to work,
but staying within Access is easier.
Questions:
1. If data access pages are used, and office web components installed on
systems without MS Office, are data access pages enabled for data entry on
those systems, or just data display? If just for display, would installation
of an Access runtime on such a system enable data entry? Access help
describes View-only mode for office web components, but only lists
spreadsheets, charts and pivot tables. The application woud only expose
forms and parameterized reports as data access pages.
2. What type of data integrity and repair is available with MSDE, such as
with power or non-hard disk hardware failure? The level available with Jet
is probably sufficient, and the automatic recovery of postgresql is even
better.
Thanks,
David P. Lurie
An electronic medical records system for my office is being developed, using
Jet for the initial prototype. The eventual production version may need to
use a different backend.
The number of users at any time will be light, less than five, but the
database size will eventually grow past 2GB. Data once entered would rarely,
if ever be changed, but old data needs to be available for queries.
Archiving records yearly to new Jet or MSDE databases would keep the size
within limits; I was planning to use UNION queries to concurrently retrieve
data from archived years. The office server runs SCO OpenServer 5.0.7, such
that it can't run IIS, but the number of users is low enough that IIS on my
XP system could host data access pages.
Replication (or possibly just one or two local and remote(LAN) scheduled
database backups per day) is needed to ensure system availability in the
event of hardware failure. Remote access via VPN is needed for both myself
and my transcriptionist. That would require MSDE or postgresql rather than
Jet, unless data access pages are used.
I've gotten client-server functionality from access to postgresql to work,
but staying within Access is easier.
Questions:
1. If data access pages are used, and office web components installed on
systems without MS Office, are data access pages enabled for data entry on
those systems, or just data display? If just for display, would installation
of an Access runtime on such a system enable data entry? Access help
describes View-only mode for office web components, but only lists
spreadsheets, charts and pivot tables. The application woud only expose
forms and parameterized reports as data access pages.
2. What type of data integrity and repair is available with MSDE, such as
with power or non-hard disk hardware failure? The level available with Jet
is probably sufficient, and the automatic recovery of postgresql is even
better.
Thanks,
David P. Lurie