Access Training

[Jim]

Does anyone have any suggestions about a good source for Access training?
Thanks, Jim

 

[Todos Menos [MSFT]]

learn SQL Server.

MDB has been obsolete for a decade

-Todos

 

[Allen Browne]

See the tutorials on-line or Access books on-line:
http://allenbrowne.com/links.html

Or, for a free 30-page document covering Access basics:
http://allenbrowne.com/casu-22.html

 

[Todos Menos [MSFT]]

Access MDB is for mother ****nig babies and retards

learn SQL Server if you don't want to be stuck making $12/hour

 

[Larry Linson]

Does anyone have any suggestions about a
good source for Access training?

Follow the "Training" links at http://office.microsoft.com for good "getting
started" information. You'll also find suggestions for books, self-study
and reference, at http://www.mvps.org/access. In doing some searching for
Access 2003 training material for a client, I was disappointed to find that
at least one of the reputable providers of training material had not updated
their Access courses since Access 2000.

I know some people who are currently negotiating to prepare course material
for Access 2007, but that means it will be some time before those courses
could be published. Other providers will be on different schedules, and I
haven't done any searching on availability or commitments for availability
of third-party training for Access 2007.

Larry Linson
Microsoft Access MVP

 

[Guest]

What about advanced courses? I can not really find anything. Even classroom
based would be fine.
I am searching for a co-worker who is insisting on making Access work like
an object based tool, more like PowerBuilder, and using linked lists and such
as opposed to an actual relational database. Needless to say, the coding is
getting really cumbersome and it is all the fault of Access. (Having to use
forms that are never seen in order to store the user defined collection of
things from another fomr, etc.....)
My boss thought that if they had some advanced training, they may understand
the tool better.

Any thoughts?

 

[John W. Vinson]

I am searching for a co-worker who is insisting on making Access work like
an object based tool, more like PowerBuilder, and using linked lists and such
as opposed to an actual relational database

"There are none so blind as they who will not see..."

John W. Vinson [MVP]

 

[Guest]

good quote!!! not much help on training ideas though... ;-)

so, what is a good argument against linked lists vs. database structure. to
quote "i bet most Access programmers won't even know what a linked list is,
this product is not a real development tool."

any ammo is appreciated!

 

[John W. Vinson]

good quote!!! not much help on training ideas though... ;-)

so, what is a good argument against linked lists vs. database structure. to
quote "i bet most Access programmers won't even know what a linked list is,
this product is not a real development tool."

A linked list is an excellent tool... for projects where a linked list is
appropriate. A drill press and a table saw are both good tools, but you
wouldn't drill holes with a table saw - or manage data retrieval and reporting
with a linked list! Nor would you really want to use Access to set up a
dynamic internally-threaded linked list; you *could*, but it's not really the
right tool (you'ld do it in C or C++ or C# or some other programming language
at far more complexity and effort).

Not knowing what your colleague is trying to accomplish, I can speculate that
*either* the project is one where a linked list might indeed be apropos; or
that he's one of the people who know how to use a hammer, so every problem
looks like a nail.

John W. Vinson [MVP]

 

[Guest]

ah, well, i am thinking you have come across these types before. because the
hammer analogy is perfect. exactly perfect.

the application consists of an initial set of data. once that initial set
is changed, at all, it becomes a new set. the new set may be changed, but
all changes to this are to be tracked. even if it is just one record. then
another new set may be made, voluntarily, and all those changes tracked.
etc.... this should be able to happen forever.
once it is done, it is done. the user would start with a brand new set of
data, and repeat.

not saying linked list isn't a good way, i am a relational database person,
and don't always want to use a hammer, so i am open! it just is that the
coding on this project has become insane, and i am attempting to help where i
can. and a a bit tired of "Access is trash and can't do real database"
statement.
forms are bound to the nines, nothing refreshes properly. it is really a
bit of a nightmare. it is working, but when/if i have to come in and make
changes, it will be really, really difficult. never seen so many user
defined collections in all my life.

thanks, love the hammer analogy!