Michael
2012-05-10 08:09:42 UTC
Just looking for a little guidance here. I work for a small law firm, and we currently use a software package for practice management (open/closed files, calendar, phone messages). Unfortunately, we have had nothing but problems with the software (and from what I see online, most customers do). Furthermore, it just isn't designed to do what we need/would like it to do for our practice.
SO I've decided to design my own program to suit our needs to a "T". I've been exploring options for the past week, and would just like an opnion or two (or three, or five...) from people with more experience.
As it stands now, I have exported our data into Access 2010 tables (Clients, Courts, DA's, Files). I'm looking to have the following features: track open/closed files (files are linked to a contact, have a court and DA assigned from drop-down list), maintain an office calendar (court dates linked to respective files), have a module of some kind to track phone messages, and document generation (much of what we send are form letters; rather than typing information each time, have court address & client name/case number pulled from tables).
I would like this all to be web-based & stored on our server, so no installation is required and it could be accessed remotely. I began to design everything in an Access Web Database, and was very happy with the product - until I realized that it would require purchasing SharePoint Server Enterprise - again, this is a small firm, our "IT budget" is not exactly Enterprise-sized.
After some research, it seems that my best option is to upsize my Access database to SQL Server and then use Visual Studio to design an interface to do as I wish. It's been a while since I've used VS or done any programming (outside some light web work), but through the years I've never had a problem teaching myself anything I need to know. I guess my question is -- would this setup (SQL/VS) allow me to do everything I'm looking to do? If not, is there a better option?
If we have to purchase SharePoint, so be it... but I must admit, I'm a little excited to do some programming.
Sorry for being so long-winded, any help or advice anyone can provide is HUGELY appreciated.