General discussion


Can it be done?? Rework frontend to Web..

By Whatme? ·
I assume it can be done but at what costs *hrly/daily etc.) and where do I go to find a qualified person(not me for sure) that can do it.
I have a database (30-50 mg) on an SQL 2000server. The client side software is written in VisualBasic. Every time I need a change our developer charges an exorbant fee and takes weeks. I need someone to rewrite or create from scratch a complete web enabled feature to access, update (depending upon users). This frontend now saves a local copy of the database on each workstation in an access type file. Unfortunately, we own the frontend but do not have access to the code... just the compiled version. I would even entertain thoughts about moving our database over to MySql (the thoughts of upgrading a future MS version makes me ill.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

No Smart people out there?

by Whatme? In reply to Can it be done?? Rework f ...

Obviously not. I guess I am on the wrong site. I ask for help and get nada.

Collapse -

by barneyrubble318 In reply to Can it be done?? Rework f ...

I wouldn't move to MySql. It's not very compairable to MS SQL Server. The upgrade is not that bad. (7.0 to 2000 is a snap.) Last I heard, MySql doens't have Foreign Keys in the current version, in my opinion this means it is not even a database.

If the db is only 30 to 50 meg it can't be that difficult to backwards engineer. Talk to the users and see what they actually use of the front end. Get familiar with the data.

VB is a fine front end, you just really need the code. I'd probably can the idea of a local cache of the database.

Sorry no one replied, but this is kind of an open question.

Collapse -


by Whatme? In reply to

I guess I will just plod onward. Like I said before, I really hate being a captive of MS. It seems to just get worse and worse. I really wanted to see a web interface so that I woldn't have any software on a workstation. That way I could use any OS

Collapse -

Web interface

by DPJ In reply to Onward

I prefer a Web interface over VB, Java, C++, .adp, etc. in most cases because you do not need to worry about licensing issues. That being said, security concerns go up--as well as--development time (where .adp can be exploited).

To answer your original question...without more information about the types of transactional forms you would need, number of users, do history tables need to be implemented, what connection speeds are your users using, is it an Public site, Intranet, or Extranet, etc. it is difficult to answer and so we all do not. In addition, does it need to be reported, backed up, etc.....

We would like to help, but the first step is to identify what it is you need (requirements building).


Collapse -

I want to do the same.

by ma407 In reply to Can it be done?? Rework f ...

We have a backend server SQL server. Our front end is written in Visual Basic. We need to do things the SOFTWARE company REFUSES to do.

I wanted to do it web based, but I'd have to add another server, put IIS on it and write the code in PHP or ASP..whatever.

Turns out, writing code in Visual Basic is easier.They have many books out there. PHP and AsP I think do not have reuse such as an object oriented program such as VB classes. Learn the front end.. it only takes TIME.

go for it

Collapse -

VB is not object oriented !

by Tony Hopkinson In reply to I want to do the same.

That aside writing a web based front end for a database is no more or less complex that a clientside gui, the difficulties just move about a bit.
You can achieve a lot better GUI in VB than you can in a web application (unless you want to use clientside ActiveX) or buy in things like serverside graphing etc.

Collapse -

Well your question is a tad confusing

by Tony Hopkinson In reply to Can it be done?? Rework f ...

If you do not have the skills in house and you don't own the source(how did that happen ?). It won't be any less expensive or time consuming. If you had owned the source then your current developer would have had to compete, similarly if someone wrote a web based app they would have to compete as well.
If you had the time and skill you could learn VB , PHP whatever and maintain it yourself, if you owned the source.
The tech is not the problem, your company putting it's nuts in a developers vice is.
Can't say I blame them though, when you find a cash cow, it's very impolite not to give it a good milking.

If I was you I'd look at putting together your actual requirements (include web based as a requirement if you want) and put them out to various firms for quotes. Include your current mate (he might realise your udders have dried up), but whatever you do and whoever you go with make sure the source is a deliverable.

Oh and if you aren't going to have in-house skills , set up a maintenance contract on your source, offer the first year or so to those who give the job to. Software firms make money off upgrades, not the initial development and they'll want to keep that contract.

One more point, it might be wise to get an independant consultant in to check out that the eventual vendor isn't taking advantage of your ignorance, a bit of obfuscation on their part will help them keep your contract, in that any other developer will find it very difficult to take on the code, no matter what it's written in.

Related Discussions

Related Forums