gmg said:
I've been reading so much on this subject, I think I'm getting very confused.
I would agree with your self assessment. said:
Is there a difference between Replication and Sharepoint?
Access and SQL Server both have replication as part of their feature
set. Sharepoint has some offline table stuff it can do. Not sure
exactly how similar that is to replication but it's getting close I
think.
I had thought that the program had to be in the ACCDB format in order to use
Sharepoint.
I don't know.
And I thought I needed to use Sharepoint to do Replication.
No.
I would like to use SQL Server but it seems like the learning curve is quite
high. The company that wants this done wants it as soon as possible. If
they go with SQL Server, they want to use SQL Server 2008 Express because
it's free. I'm not sure if it does Replication the way we need to (it only
does Subscriber?)
I'm not sure if I need to recommend to them to buy a version of SQL Server
or just go with Sharepoint.
SharePoint is aimed at a different set of users than Access or SQL
Server. If you want relational integrity and large datasets then you
need SQL Server. Also to upsize a system to using SQL Server is
likely a lot less work than figuring out how to adapt your application
to Sharepoint and how it works.
I should add that while there's a lot of very interesting stuff
happening with Access 2010 and SharePoint, see the MS Access product
group blog for more information, I'd still go with SQL Server for an
internal use application.
Now if this was an app with non employee type of users via the web
then I'd look at Access 2010.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see
http://www.autofeupdater.com/
Granite Fleet Manager
http://www.granitefleet.com/