why visual basic better than access-please respond!!!

[AccessNovice]

1. I would like my company to use vb instead of access. They fear any change unless some good arguments. One plus in access would be that a form's textbox in runtime say displaying a number 104 from the table...you the programmer can change it to 103 and the change is also in the table. How can a vb programmer(w. a sql7 db) do the same so easily? Plus too is there is no connection to sql7 code needed-just the control and record source of the form and its textboxes. You don't have to learn another reporting tech. Access has wizards to help build reports, etc.
I would like anyone to help my argument in using visual basic 6 as a front end...why is coding in vb better than access, what can a programmer do in vb better than coding in access, what technologies can vb use that access can't...

Please all you visual basic programmers give me some ammo to win my company over in getting into vb!!!

 

[MichaelRed]

IMHO, it is more a matter of 'taste' than substance. Each has it's (small) strenghts and weaknesses vs the other.

An example: VB allows more-or-less direct access to the printer object. You can directly set the print position, forn, font size and even draw your own graphics. POSITIVE!

You NEED these capabilities in VB, because the report generation capability is lousy (and THAT is just being NICE). Even using "Crystal Reports" et al is more effort than Ms. Access report generation.

As far as daa access goes, VB forces you to make a decision as to which (if any) db you use, while Ms. Access lets you just 'drift into' the Jet db engine. I personally would prefer to use the 'Industrial Strength' ones (Oracle, SQL Server ...) but Ms. DOES seem to be supporting the improvement to "Jet" and it is quite capable for samll to medium databases. It also makes a GOOD "Demo" db for ines which you woould like to Scale up to the more robust ones.

The ONLY serious downside to Ms. Access is just that it has been used by some serious screw-ups who in turn blame the product for the efforts of the person. This -in turn- has given Ms. Access a LOT of (mostly undeserved) bad press, so in many organizations, putting Ms. Access on your resume says you are NOT a professional Programmer to the HR AND IT departments.

MichaelRed
mred@att.net

There is never time to do it right but there is always time to do it over

 

[tsuji]

Each tool acquires its practical value according to the mission you set for it to accomplish. It is hard already by that to contrast access with vb.

Besides, there is a cost-tag for a switch over which may be substantial.

If you think your skill in vb would earn you a special technical exponent in your company, I believe you would be much better appraised if you advocate, instead, for putting both to good use rather than vb replacing access.

regards - tsuji