Database developers?

[jonathanc]

I'm pretty sure you can. IIRC Access has an "Export to SQL Server" type of functionality. Or it might be SQL Server that could import from Access. Either way, I did that sort of thing in the early 2000s so I'd be surprised if it wasn't straightforward using later versions.

 

 

Web development isn't necessarily more advanced: in some ways it's less advanced than conventional applications like a C++/C#/Java program. Web development gives you the ability to easily roll out the software (including updates/bugfixes) to users all over the world. If a user anywhere in the world has a PC with a connection to your webserver, chances are they'll be able to start using your application with little or no faffing about. It's a double-edged sword though. You'd have to protect against prying eyes, and you don't have full control over exactly how your application will look to the users (you'd be at the mercy of the browser writers: Mozilla, MS, Apple, Opera, etc).

 

From what you've said, I think a SQL Server backend with an Access frontend would be a good first stab. Just bear in mind that the frontend (the bit that you're most likely to need to upgrade if the application takes off and grows) isn't easily portable, and would need to be re-written if Access was deemed not to be suitable anymore (main reasons: used by geographically diverse users; used by staff in the field; users don't have MS Access and can't/won't install it). As Gav said, lots of applications start off as Access databases, and stay that way because they're too cumbersome to port to something more suitable.

 

The Reporting features in MS Access were traditionally a weak point. Maybe they've been improved now, but it's worth checking that MS Access reports give you sufficient functionality to display what you want.

 

Cheers for the brilliant input mate. Really helped me there. I don't think there will be problems with people using the system in the field or worldwide distribution as it is mainly used by staff in local offices. All PCs have proper Office package licensed distribution.

 

The only problem is multiple user access and high volume file I/O which I am sure SQL server 2008 can handle. I am also sure if one day Access is deemed not suitable for front end it would be easy to port to C/C++ or even C# based solutions in the future whilst maintaining SQL Server 2008 as back end?

 

By using Access at the moment gives me the freedom to actually develop everything in Access first while slowly work on the SQL Server database so I can roll out solutions first and import tables in SQL Server 2008 when ready.

 

Only thing is they might want to implement in the future is to enable the production staff on factory floor to have a wifi tablet to receive updated manufacturing information in the future but I am sure there's a simple way of handling that using a web browser just to access specific part of the database perhaps?

 

edit: As for reporting, I have so far found the various graphs and charts useful. I think it would be simple to extract related information and then use Excel for further reporting usage if needed. The Reporting side is mainly for managers to monitor specific KPIs etc.