Need some Progamming Platform Input. Please Help

[calpha]

i've been working for a cheap client for two years managing (read putting out fires, and modifying) a custom application that they've designed for their industry, in the engineering field.

It's basically an Inventory Management System with highly advanced crystal report capabilities, created in VB (ack) and Access. They are generally computer idiots, and do not know how to build a product, and aren't willing to pay for something they don't understand (ie, moving to ADO, adding On-Line Help, adding Multi-User access). The application is written to have one database per machine, but does give the ability to Import/Export records so that machines can share information.

I've been working on a plan to completely redo this application, and then sell it back to them, and this is where I've run into a delimna.

Ideally the application would have a shared database for the users in each office to use. Also, it would include either a Pocket PC or PALM addon for inputting information while on-site doing surveys. Whether or not this is a WAP application would be based on other decisons.

The main goal for this application is to keep the expense at between lower then $1000 for each install, and then add a user and site licensing fee on top of that.

That being said, here's what I'm having a problem with:

• 
  The database. Access is not a viable option for shared databases, and I am not going to use it in that capacity. Expense is another pre-req, so I'm leaning towards MSDE, which provides another problem. 2 gig data limitation, and 5 simultaneous users. The data limitation isn't that much of a problem, but the user number probably would be. But, a plus of using MSDE, is that I've already got a tested solution in place for installing the server piece, and client piece (installshield developer 7.0) that works

• 
  Having multiple offices wanting to share information. If I go with a One DB per office setup, then I'd definitely be using Biztalk to sync records over the internet between offices. I can't think of an easier way to do that

• 
  Also, with a one-DB per office setup, the application would also permit data syncing via the POCKET PC, no WAP.

• 
  Conversely, the concept of a web service has entered my mind, but I really like to stay away from Bleeding edge technology. Something with a hosted SQL Server setup sending data back to a thick client using SOAP. That way there's only one person (me) to keep up with the databases, because I fear having to support a "Server" in an office-setting where they don't even understand the concept of a domain vs a workgroup (very common in thier industry). However, besides cost, having no experience with securing a web-service setup (on the host side) really scares me.

The last option is a pure web setup, but that becomes troublesome too because of the reporting requirements. Crystal does have a web reporting capability but it's nothing compared to what you can do on the client side.

I would really like some feedback, or input to help me decide because I need to get started on whatever I'm going to do yesterday (already have the data model thankfully). The thing is I think an MSDE setup would be easiest to maintain (no security issues), but hardest to troubleshoot, whereas a web service, or web site would be hardest to maintain, but easiest to troubleshoot. Again, the average user is not going to know jack about computers or OSes (but like I said, they don't have to, because my install solution is seemless)

Thanks for any input,
Chris

 

[EagleKeeper]

Have been in a similar situation.

You can take your Access DB and move it into a SQL system.

Each user can have a front end client that attaches across the local network to the SQL system.

In one app I had the client for the remote user grab a copy of the DB before departure and generated records. Upon return, the new records were resynchronized into the main DB. In another app, the client only grabbed what was required from the DB, was running on a Windows CE handheld.

I never had to worry about synchronizing the DB between offices, however, the smart client option was essciently simulating the BizTalk. (This was before MS had such grand Internet plans).

The biggest problem I had was a "smart" user making a backup copy of the DB on their local system and then accidently using it, while others were using the master DB.