Front-End Back-End what to use?

Matt_Hirst · 10 Nov 2009 at 18:37

Have an existing application, not written by me and there is no documentation, that requires major redevelopment for use in a multi-user environment, currently its a stand alone application, it will be accessed via LAN and WAN with max number of potential number of users being 10 - 15. Max number of records approx 10,000.

Now the existing application is a VB6 front-end and MS Access backend.

The new IT system the application is to be installed upon has known issues with using MS Access as a backend, I believe there are timing issues when using Access as a backend where connections timeout, so the new system can use either Oracle or MS SQL Server and it is upto me to decide on the front-end.

So what would you guys use as the front-end / back-end? Requirements are that whatever is used has to be fairly easy to pick up (work will send me on a course if needs be), I come from an Access background and dabbled with VB.NET AND VB 4 - 6, support multi users and finally be a good thing to add to my CV (well I might as well get something out of it).

Specs a bit vague but hey this is the hand I have been dealt.

regards,

Matt

P.S. Forgot to add if you could point me in the direction of some online learning for whatever your suggestions are it would be appreciated.

Matt_Hirst · 10 Nov 2009 at 19:00

What does it do - well it's a basic scoring system, performance monitoring database. Guess you could say you record people against certain tasks and can then compare them - sorry I have to be quite vague on this.

regards,

Matt

Matt_Hirst · 11 Nov 2009 at 21:23

Have been having a look at SQL server and php to act as front end, both seem quite straight forward to use.

Topbanana, no its not a business critical app, but is important.

regards,

Matt

Matt_Hirst · 16 Nov 2009 at 15:34

We now have integration problems so it looks like this app will have to run on standalone laptops until the networkm integration is sorted out.

The main thrust of the existing application is a database backend and the beauty of the existing app is that we can create a database and transfer an empty copy with the front-end app and it'll work.

A rather stupid question:

With SQL server would we have to have SQL Server installed on each of the stand alone laptops?

Obviously the cost side of this would be rather huge, compared with the existing application. What other options could we use in this case?

regards,

Matt Hirst

Matt_Hirst · 16 Nov 2009 at 15:53

Just looking at SQL Server - what restrictions are placed on developing a database in SQL Server express 2008?

regards,

Matt

Matt_Hirst · 16 Nov 2009 at 16:20

Each user would have there own database and front-end and then email the data back to a central database.

Yes I can see a faff with regards data sychronisation at the central point but each remote user would see no change to what they do with the existing set-up.

Or am I missing something?

regards,

matt

Matt_Hirst · 17 Nov 2009 at 07:52

Guys, the problem is restrictions on the IT side of things which we have no control over - lack of software on the network, no databases will be available to utilise on the network for at least 1 year.

Topbanana, whilst the data held will be the essentially the same it will only be relevant to the remote site so therefore all unique to that site.

I can see what the issues are, but am having to make the best of a very bad job, but still have to come up with a solution of some sorts no matter how lame it may be.

regards,

Matt