Someone Please Set me Straight

D

Dalhart Dobbs

I am an assistant principal of a high school and I have desinged a database using demographic and schedule information exported from our program we use at school (SASI xp). I did this so the data could be used to keep a database of disciplinary information and parent contact records. My question/problem is, do I design the program strictly using access as the primary program or do I use Visual Basic as a program and tie in the data from Access, or do I just use Visual Basic??? Can someone tell me which to use and why?
 
J

John Vinson

I am an assistant principal of a high school and I have desinged a database using demographic and schedule information exported from our program we use at school (SASI xp). I did this so the data could be used to keep a database of disciplinary information and parent contact records. My question/problem is, do I design the program strictly using access as the primary program or do I use Visual Basic as a program and tie in the data from Access, or do I just use Visual Basic??? Can someone tell me which to use and why?

As a rule of thumb, if you compare an Access app developed by someone
competent in Access with a Visual Basic app developed by someone
equally competent in VB, the Access app will take between one third
and one half the time. It will be more specifically tailored to the
user's specs, and it will not require that all users have Access
installed... but it will be a lot more work (or cost).

For a developer new to both Access and VB, I'd say the VB app would
take five times as much work as the Access app.

Access is QUITE capable of creating a database, user interaction
forms, validation, flexible reports, and the like. VB can do all of
this too but needs someplace (Access, SQL/Server, MySQL, ...) to store
the data. I'm biased (I'm a competent Access developer but not yet a
competent VB developer <g>) but I'd say use Access unless you have a
very specific need and are willing to put in the extra cost.
 
P

Peter van der Goes

Dalhart Dobbs said:
I am an assistant principal of a high school and I have desinged a
database using demographic and schedule information exported from our
program we use at school (SASI xp). I did this so the data could be used to
keep a database of disciplinary information and parent contact records. My
question/problem is, do I design the program strictly using access as the
primary program or do I use Visual Basic as a program and tie in the data
from Access, or do I just use Visual Basic??? Can someone tell me which to
use and why?

Jeff has alluded to some of the major considerations, especially that a
system developed in Access will require that all system users have MS Access
installed on their PC's (unless, of course, you have the developer edition
of MS Office and intend to use the Access runtime).
Here are some other basic considerations:
How much data will be stored (number of tables, project row count in each,
etc.)?
How many concurrent users do you envision?
The Jet database engine is designed for individual user or small workgroup
systems, not for enterprise-level systems. Not knowing the size of your
school, and not knowing the intended user base, I cannot tell you if Access
(the database) is a good choice for you.
Developing in VB requires considerably more technical knowledge than
developing in Access. Access (the development environment) is designed so
non-IT people can put simple systems together.
I have one last point. No disrespect to your technical skills (I have no
idea, as you didn't say), but when somebody says they "designed a database"
and I don't know their background, the first thing I do is ask to see their
table layouts and a relationship diagram. Why? Because a database system
using non-normalized data is almost certain to fail (if it ever gets
finished). Getting the data design right is crucial.
Please post back with additional details you wish to share and any
additional questions you have.
 
J

John Vinson

As a rule of thumb, if you compare an Access app developed by someone
competent in Access with a Visual Basic app developed by someone
equally competent in VB, the Access app will take between one third
and one half the time. It will be more specifically tailored to the
user's specs, and it will not require that all users have Access
installed... but it will be a lot more work (or cost).

An Esteemed Colleague pointed out that my wording was unclear here.
I'm suggesting that developing in Access will be faster and cheaper
than developing in Visual Basic.

The advantage of VB is that you don't need Access on each user's
machine, and that the application can be more customized. It's just
that this advantage comes at a substantial cost.

Thanks, Larry!
 
A

Arvin Meyer

Dalhart Dobbs said:
I am an assistant principal of a high school and I have desinged a
database using demographic and schedule information exported from our
program we use at school (SASI xp). I did this so the data could be used to
keep a database of disciplinary information and parent contact records. My
question/problem is, do I design the program strictly using access as the
primary program or do I use Visual Basic as a program and tie in the data
from Access, or do I just use Visual Basic??? Can someone tell me which to
use and why?

----
Unless you are an experienced programmer, there isn't even a choice. While
an inexperienced database developer can make a big mess in Access, he/she
may still get something resembling a database produced. An inexperienced
user trying to be a programmer cannot do anything approaching a database
using Visual Basic, or even less using the current iteration, VB.NET. I have
experience working in an environment of both skilled Access and VB
professionals. The experienced Access developers consistantly produce
databases 3 to 6 times faster, depending mostly on the complexity of the
application. Web applications typically take closer to 5 or 6 times as long
as Access front-ends.

Microsoft's stated Access specifications are 255 concurrent users and 2 GB
of data. Do not count on those statistics. An Access database, which is well
designed can comfortably support as many as 4 dozen active users and
hundreds of MBs of data. Under read-only conditions, many more users and
much more data can be supported. I have personal experience that attests to
those figures. On the other hand, unskilled designers can produce a database
that may work beautifully for a few users who are careful with the data and
hardware.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top