Probably an easy question for an expert :)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Shouldnt think you'd need SQL server although I would consider it if you're
50% sure you might expand it in the future.

Anything else you need to know?
 
1. Access is a realtional DBS (database management system).
2. Access was initally developed to allow managers (people with the office
programs on their machines to "access" disparate corporate data).
Therefore, it comes very strong in the find data, display data, report data
areas, Fair to Good (but not bulletproof) in data storage.

3. Keep in mind the only reality in Access is tables -- they are the only
place your data is stored, all else is illusion!

Access Objects:

Tables -- store data (they are not for data entry)
Relationships -- tie tables together using primary and foreign keys
Forms -- Display data, add data, edit data, and sometimes delete data
Queries -- Table like in that they select data to display in forms or
reports.
Reports -- Print out data or in preview mode can display data
Macros -- code like things that allow those of us that are not programmers
to do some really neat (dangerous) things.
Modules -- this is where the VBA code lives.

Did I mention tables are not for data entry?

Now to answer your questions.

1. For a non-programmer, not familar with relational databases, I would
start with Access then move up to SQL server, unless there is some driving
need for a large distributed application.

2. Your application sounds liks a simple inventory control problem and is
easy to implement in Access, there are even several examples posted about.

Ed Warren.
 
Thanks to you and Ed,

I was simply wondering which would be best to get familiar with since both
options represent a "Learning curve" from what I have been used to, and that
some time ago :).

Not being too familiar with either I guess I was wondering whether there'd
be more versatility starting out with SQL - there's no real need for multi
user but it might be handy to have access from more than one machine. I
think I'll give it a shot both ways here at home and see what kind of
trouble I can get into :).

Charlie
 
You may one to have a look a a software called SuperBase also. It is
similar to your DataEase in that Tables and Forms are designed together.

Access is certainly more powerful than SuperBase but from what I heard,
SuperBase is fairly simple to use for small databases.
 
Many years ago I used a product called DataEase (Sapphire Systems then) to
write a Dos based system and found it intuitive and easy, but I do not like
their Windows based system because, to me at least, it's too graphical and
nowhere near so intuitive or versatile. For example you could easily link
Tables (they called them forms because the intuitive part was form-table
automation) so that for the example below no external programming was
needed.

I did a few things with it but for example with stock control...

Product table was linked to suppliers table so I could have several
suppliers for one product and choose one easily. Similarly items were booked
out as a transaction (using a more or less ad hoc form) and so one booking
could easily pull info from the stock table and do the necessary math. The
advantage was that more or less anything could easily be done by transaction
and thus a history was kept.

I have never made a serious attempt with Access, I'm 20+ years older and
programming is not my job but I'd like to make the job easier so my basic
question is how would one go about doing something similar - for example
would it be better to use single machine and just access, or would it be
better to use SQL server (even on the same machine) or would SQL server and
VB be the only viable answer?

I think the power of DataEase came from the fact that any report could be
used to modify the tables and so giving 50 items to customer A, adjusting
stock and generating an order to supplier Z was very simple.

I should add I guess that this will be essentially a single location / user
system but the PC is part of a small business network and running an SQL
should present no major problems.

So if any experienced access users want to chip in with ideas I'd appreciate
it, we do not have to be accountable so an expensive bespoke solution is
neither desirable nor necessary.

TIA

Charlie
 
Back
Top