SQL Server, DAP's, Synchronization?

  • Thread starter Thread starter Tim J
  • Start date Start date
T

Tim J

I have a project tracking access app. It needs to be
distributed among 25 remote users. For them to Have a
front end and access the data @ a central location they
would have to vpn which is obviously a very painfull
experience.

I wonder what is the recomended design, option for what I
need. Is synchronization still as high maintenance in
access 2002 as it was in 2000 (Data Conflicts)?

How much time, effort, challenges can i expect in
transfering from forms to data access pages?

I need a fast, cheap, reliable solution.

What would you recomend?

TIA,
TimJ
 
I built a DAP a few years back that worked pretty well over a VPN to a SQL
Server database.
It was a single screen that allowed searching, entering and editing of
records.

A VPN is not painful (for me). I have good Cable connection to an office 300
miles away.

If you have 25 remote users you should consider a ture Web application and
let them hit a web server over the Internet.
The DB could be anything (.mdb, SQL Server, Oracle, etc.) I know many people
who have sucessfully used .mdb files for small web apps so don;t let anyone
tell you it can't be done. But I would use MSDE (SQL Express is the newest
name, isn't it?) This is a cheap (free?) version of SQL Server that will
easily meet your needs.

You can use ASP or ASP.Net instead of Access DAPs which are kind of hard to
work with and get running over the Internet. Also, DAPs have not been
improved since they were introduced so they are sort of obsolete.

Good luck!
 
Back
Top