Hi,
I am developing a church management solution in VB 2010 / SQL Server 2008. I want one computer in the church to run the main database, but have laptops with the application installed able to go home with the data and be able to modify it, and then sync when the user returns to work the next day. Then while at work and connected to the LAN everything would just run as normal, like a client-server type application. The application as it stands uses triggers, stored procedures, views, and functions heavily. When I started looking into the occasionally connected database scenario, I am not sure it will still support all of this functionality. When I started development, I was looking only at the client-server aspect.
Thanks for any help...
Joe Fager