Moving to Visual Studio 1

[SeeThru]

Hi All

I'm considering moving some Access databases to visual studio .Net, with MySQL or SQL backend.

The applications are only used internally (PCS on the network). We have a lot of smaller database that change design pretty regularly - forms are modified, new fields added, etc.

What's the best option for this - a web based interface or a traditional published program?

SeeThru
Synergy Connections Ltd - Uk Telemarketing and Telesales Services and
Synergy Mobile Solutions - UK Mobile phones, land lines and call packages

 

[jrbarnett]

What do you hope to get by moving to Visual studio? Better security/reliability/scalability, experience in .Net languages, Upsizing from Access?

Whether you go for a desktop or a web app also depends on whether all of your users will be using windows PC's or if you have any Macs or Unix machines, or if you need remote access (in which case a web app can be far cheaper than a Citrix or terminal services desktop).

John

 

[SeeThru]

Thanks for the response.

It's partially scalability, and also to get away from using obsolete Access97 (we do not have licences for later versions). If we develop it in-house, it will be a cheaper option than buying all the licences and converting to a later version of access.

It will give us some new bells and whisltes as well, with better reporting and backup options.

It will be run on local PCs - usually Win2k or XP - with very basic specifications. Remote access is not partocularly likely, although a web version could be built to point to the same data in the future.

SeeThru
Synergy Connections Ltd - Uk Telemarketing and Telesales Services and
Synergy Mobile Solutions - UK Mobile phones, land lines and call packages

 

[JoeAtWork]

If you are making frequent changes I think a web interface is probably better - that ensures everybody is always using the most current interface.