New to Access

I work in the parts department of a new car dealership. We ar
frequently asked by customers for fluid capacities and types of thei
vehicles. Unfortunately this information is not in our parts catalog
so we must obtain the information from service manuals in the servic
department. I had the bright idea to gather this information and pu
it in a database, so I purchased Access. I have studied som
information regarding relational databases and I have a
understanding on relationships, however I just don't know how to pu
it to practice. For example, a 2005 Explorer has more than on
engine choice, transmission choice, front and rear axle choice etc.
Also these different engine, transmissions, etc. may fit differen
years and models. Would this constitute a many to many relationship
What key field would I use to gather all the related informatio
together? I like to create a form that would gather the year, mak
and model from a user and display all the fluid capacity and type
for that vehicle. Any help on getting me started in the righ
direction would be greatly appreciated

re: New to Access

brink wrote:[color=blue]
> I work in the parts department of a new car dealership. We are
> frequently asked by customers for fluid capacities and types of their
> vehicles. Unfortunately this information is not in our parts[/color]
catalog,[color=blue]
> so we must obtain the information from service manuals in the service
> department. I had the bright idea to gather this information and put
> it in a database, so I purchased Access. I have studied some
> information regarding relational databases and I have an
> understanding on relationships, however I just don't know how to put
> it to practice. For example, a 2005 Explorer has more than one
> engine choice, transmission choice, front and rear axle choice etc.
> Also these different engine, transmissions, etc. may fit different
> years and models. Would this constitute a many to many relationship?
> What key field would I use to gather all the related information
> together? I like to create a form that would gather the year, make
> and model from a user and display all the fluid capacity and types
> for that vehicle. Any help on getting me started in the right
> direction would be greatly appreciated.[/color]

Strasser replies:
This will be a good "thread" for anyone NEW to relational database
design who wants to use Access to create the database FROM SCRATCH.
I am a teacher so the discussion will differ from the normal short
answer format.
Brink, you have stated as the database objective that you want to be
able to input automobile:
1) year
2) make
3) model of the car
and display all the
4) fluid capacities for different types of fluids

QUESTION:
By fluid "types" do you mean:
oil
brake
automatic transmission (or manual transmission)
coolant capacity
These kinds of "types"?
Please answer this question.

First step in design of a new database
It is important to know what you want OUT of the database.
Is the above accurate?
What format do you want the information in?
(sounds like a screen display of a form showing fluid capacities
of the different fluid types, so you can answer the customer when they
ask for types and fluid capacities for their cars)

Please answer my question about "types".
If anyone else is going to follow this general database design
discussion, please "reply" so we know others are following along the
discussion.

Brink, I'll look for your answer. Strasser

re: New to Access

Brink,
Parts made up of parts, is that pretty much what you need to remember? What
parts made up which other part? If a customer bought a 2004 Ford Explorer
with the 4.6 Litre modular V-8 it gets 7 quarts of 20W-50 because that
engine with the trailer package came with a larger oil cooler, for example?
Pretty much the basic design is a bill of materials. You only need a simple
bill of materials so probably it's one finished vehicle has some parts that
went into making it--or a one-to-many relationship. Fluids would be treated
as parts in this example. So, you only need one table listing all the
relevent parts. In one of the columns of that table will be a PART_NO that
uniquely identifies that part. In a second column will be BELONGS_TO which
contains the part number of the part that this part belongs to. The rest is
whatever attributes of a part you need for your purpose. Unit of measure
and units needed are probably two additional columns.
So, for example:
PART_MASTER_TBL
PART_NO Text(15) Primary Key
NAME Text(50)
DESC Text(255)
UOM Text(15) Foreign Key UOM_LKP On UOM_LKP.UOM_CODE Text(15)
UNITS_NEEDED Single
COMPONENT_OF Text(15) Foreign Key PART_MASTER_TBL On
PART_MASTER_TBL.PART_NO

The description above should give you an idea. It's not completely legal
ANSI SQL so it won't make a table without some work. But the ideas are
there.

re: New to Access

That said... read this...

http://www.mvps.org/access/modules/mdl0027.htm

re: New to Access

Pietlinden,
Cool.

<pietlinden@hotmail.com> wrote in message
news:1111965711.079957.217580@z14g2000cwz.googlegr oups.com...[color=blue]
> That said... read this...
>
> http://www.mvps.org/access/modules/mdl0027.htm
>[/color]

re: New to Access

1) You bought the right tool to do the job.
2) It doesn't sound like you have the technical knowledge of relational
databases to do this project and make it run like the fererri It should be.

-BrianDP



"brink" <brink@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
news:2aydna7hOe_K7tvfRVn_vA@giganews.com...[color=blue]
>I work in the parts department of a new car dealership. We are
> frequently asked by customers for fluid capacities and types of their
> vehicles. Unfortunately this information is not in our parts catalog,
> so we must obtain the information from service manuals in the service
> department. I had the bright idea to gather this information and put
> it in a database, so I purchased Access. I have studied some
> information regarding relational databases and I have an
> understanding on relationships, however I just don't know how to put
> it to practice. For example, a 2005 Explorer has more than one
> engine choice, transmission choice, front and rear axle choice etc.
> Also these different engine, transmissions, etc. may fit different
> years and models. Would this constitute a many to many relationship?
> What key field would I use to gather all the related information
> together? I like to create a form that would gather the year, make
> and model from a user and display all the fluid capacity and types
> for that vehicle. Any help on getting me started in the right
> direction would be greatly appreciated.
>[/color]

re: New to Access

Brian,
Access isn't really for folks that studied databases and programming in
college. On the cheap, PostgreSQL & a decent open source Java IDE like
Eclipse are probably better. If there is money to spend, either something
like Oracle or Ingres or SQL Server and a full version of Microsoft's VB.Net
or C# are also good. Access is exactly the right tool for a user like the
original poster. He can put something together in a relatively short period
of time that will help if he has a decent understanding of Excel. Things
really start to get fun when the project takes on a life of its own and he
finds himself having to invest more of his time in learning programming &
databases so he can build something that lives up to his original dream.

--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS
"ng" <ng@ng.com> wrote in message news:4y_1e.34386$oa6.8454@trnddc07...[color=blue]
> 1) You bought the right tool to do the job.
> 2) It doesn't sound like you have the technical knowledge of relational
> databases to do this project and make it run like the fererri It should
> be.
>
> -BrianDP
>
>
>
> "brink" <brink@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
> news:2aydna7hOe_K7tvfRVn_vA@giganews.com...[color=green]
>>I work in the parts department of a new car dealership. We are
>> frequently asked by customers for fluid capacities and types of their
>> vehicles. Unfortunately this information is not in our parts catalog,
>> so we must obtain the information from service manuals in the service
>> department. I had the bright idea to gather this information and put
>> it in a database, so I purchased Access. I have studied some
>> information regarding relational databases and I have an
>> understanding on relationships, however I just don't know how to put
>> it to practice. For example, a 2005 Explorer has more than one
>> engine choice, transmission choice, front and rear axle choice etc.
>> Also these different engine, transmissions, etc. may fit different
>> years and models. Would this constitute a many to many relationship?
>> What key field would I use to gather all the related information
>> together? I like to create a form that would gather the year, make
>> and model from a user and display all the fluid capacity and types
>> for that vehicle. Any help on getting me started in the right
>> direction would be greatly appreciated.
>>[/color]
>
>[/color]

re: New to Access

Strasser, the types of fluid for instance would be oil weights lik
5W20 or 5W30 for engines. Mercon 3 or Mercon 5 fluid types fo
transmissions. Green, orange, gold colored antifreezes for coolan
types etc..

re: New to Access

"Alan Webb" wrote
[color=blue]
> Access isn't really for folks that
> studied databases and programming in
> college.[/color]

Access is (really) for the professional as well as the end user. (I suspect
I qualify, as I've been earning my living as a professional programmer and
developer since 1958.)
[color=blue]
> On the cheap, PostgreSQL & a decent
> open source Java IDE like Eclipse are
> probably better.[/color]

Better for _what_? Not better for the clients who hired me to create "normal
business database applications" quickly and inexpensively. Better, perhaps,
for some situations -- in your studies "of databases and programming in
college", did no one ever mention using "appropriate technologies"? It's
quite possible that some "in the lofty halls of academe" would not because
of their lack of practical experience.
[color=blue]
> If there is money to spend, either something
> like Oracle or Ingres or SQL Server and a
> full version of Microsoft's VB.Net or C# are
> also good.[/color]

Anyone who'd use .NET instead of Access to create the UI for individual
applications or small-to-modest-sized multiuser or client-server
applications, at this point in the .NET product lifecycle, clearly needs
"professional help" for his/her masochistic tendencies.

Larry Linson
Microsoft Access MVP


Access is exactly the right tool for a user like the[color=blue]
> original poster. He can put something together in a relatively short[/color]
period[color=blue]
> of time that will help if he has a decent understanding of Excel.
> Things really start to get fun when the project takes on a life of its[/color]
own and he[color=blue]
> finds himself having to invest more of his time in learning programming &
> databases so he can build something that lives up to his original dream.
>
> --
> Alan Webb
> knoNOgeek@SPAMhotmail.com
> "It's not IT, it's IS
> "ng" <ng@ng.com> wrote in message news:4y_1e.34386$oa6.8454@trnddc07...[color=green]
> > 1) You bought the right tool to do the job.
> > 2) It doesn't sound like you have the technical knowledge of relational
> > databases to do this project and make it run like the fererri It should
> > be.
> >
> > -BrianDP
> >
> >
> >
> > "brink" <brink@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
> > news:2aydna7hOe_K7tvfRVn_vA@giganews.com...[color=darkred]
> >>I work in the parts department of a new car dealership. We are
> >> frequently asked by customers for fluid capacities and types of their
> >> vehicles. Unfortunately this information is not in our parts catalog,
> >> so we must obtain the information from service manuals in the service
> >> department. I had the bright idea to gather this information and put
> >> it in a database, so I purchased Access. I have studied some
> >> information regarding relational databases and I have an
> >> understanding on relationships, however I just don't know how to put
> >> it to practice. For example, a 2005 Explorer has more than one
> >> engine choice, transmission choice, front and rear axle choice etc.
> >> Also these different engine, transmissions, etc. may fit different
> >> years and models. Would this constitute a many to many relationship?
> >> What key field would I use to gather all the related information
> >> together? I like to create a form that would gather the year, make
> >> and model from a user and display all the fluid capacity and types
> >> for that vehicle. Any help on getting me started in the right
> >> direction would be greatly appreciated.
> >>[/color]
> >
> >[/color]
>
>[/color]

re: New to Access

Alan Webb wrote:[color=blue]
> Brink,
> Parts made up of parts, is that pretty much what you need to remember? What
> parts made up which other part? If a customer bought a 2004 Ford Explorer
> with the 4.6 Litre modular V-8 it gets 7 quarts of 20W-50 because that
> engine with the trailer package came with a larger oil cooler, for example?
> Pretty much the basic design is a bill of materials. You only need a simple
> bill of materials so probably it's one finished vehicle has some parts that
> went into making it--or a one-to-many relationship. Fluids would be treated
> as parts in this example. So, you only need one table listing all the
> relevent parts. In one of the columns of that table will be a PART_NO that
> uniquely identifies that part. In a second column will be BELONGS_TO which
> contains the part number of the part that this part belongs to. The rest is
> whatever attributes of a part you need for your purpose. Unit of measure
> and units needed are probably two additional columns.
> So, for example:
> PART_MASTER_TBL
> PART_NO Text(15) Primary Key
> NAME Text(50)
> DESC Text(255)
> UOM Text(15) Foreign Key UOM_LKP On UOM_LKP.UOM_CODE Text(15)
> UNITS_NEEDED Single
> COMPONENT_OF Text(15) Foreign Key PART_MASTER_TBL On
> PART_MASTER_TBL.PART_NO[/color]

How do you relate the 2004 Ford Explorer to the 4.6 Litre modular V-8
with a larger oil cooler using that table structure?

How about the 2003 Ford Explorer?

re: New to Access

rkc wrote:[color=blue]
> How about the 2003 Ford Explorer?[/color]

Ford. At least they circled the problem :-)

--
[Oo=w=oO]

re: New to Access

Larry,
Hi. Listen, I bow to you in terms of qualifications. I am self-taught.
The only formal education I have is eight classes at UC Berkeley Extension
some years ago. Access is a very good tool. It is a good match to the sort
of project the original poster proposed. I am still bitter, though, because
in the job market I competed in knowledge of Access alone wasn't enough to
keep me employed. So I tend to trash Access a bit.

--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS
"Larry Linson" <bouncer@localhost.not> wrote in message
news:74i2e.28245$b_6.16115@trnddc01...[color=blue]
>
> Access is (really) for the professional as well as the end user. (I
> suspect
> I qualify, as I've been earning my living as a professional programmer and
> developer since 1958.)
>[/color]

re: New to Access

RKC,
The [component of] column. Complex bills of materials use at least two
tables instead of one. A bill of material is one of the standard schemas
for storing hierarchical data. I suggested one table that would use
[COMPONENT_OF] to join the table to itself because it is the most
straightforward and simple database for a bill of materials. The original
poster was not a programmer so one requirement was to keep it simple.
--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

"rkc" <rkc@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:m3n2e.125342$H05.33686@twister.nyroc.rr.com.. .[color=blue]
>
> How do you relate the 2004 Ford Explorer to the 4.6 Litre modular V-8 with
> a larger oil cooler using that table structure?
>
> How about the 2003 Ford Explorer?
>[/color]

re: New to Access

Alan Webb wrote:[color=blue]
> RKC,
> The [component of] column. Complex bills of materials use at least two
> tables instead of one. A bill of material is one of the standard schemas
> for storing hierarchical data. I suggested one table that would use
> [COMPONENT_OF] to join the table to itself because it is the most
> straightforward and simple database for a bill of materials. The original
> poster was not a programmer so one requirement was to keep it simple.[/color]


Well, it seems the op isn't really interested so I won't pursue the
issue except to say that don't see any need for a bill of materials
to solve the problem. Complex or otherwise.

re: New to Access

"Alan Webb" <knogeek@hotmail.com> wrote
[color=blue]
> . . . I am still bitter, though, because
> in the job market I competed in knowledge
> of Access alone wasn't enough to keep me
> employed. So I tend to trash Access a bit.[/color]

Until the general business climate went South about 2000, in the Dallas -
Fort Worth area, the problem since 1994 had been finding enough Access
people to fill the demand for Access developers.

Most of my work was on Access clients to various backend server databases -
Informix, Sybase SQL Anywhere, Sybase and MS SQL Server. But there was a
good deal of demand, as well, for development of Access apps for individuall
users and Access/Jet multiuser.

There were, of course, areas where I didn't even bother trying to seek
work -- companies with some server DB who had already decided that the
client application had to be PowerBuilder, for example. And, it was always
helpful to have experience in and be skilled in collecting and documenting
requirements, writing software specs, and designing applications along with
"Access development".

Where are you and what was your target market?

Larry Linson
Microsoft Access MVP

re: New to Access

Larry,
I was in the S.F. Bay Area until 2001. These days I am in Richmond, Va. and
in the middle of writing a book on a completely different subject. My
degree is in English Literature and computers were a hobby that turned into
a career for a while. I'd go back to coding for money again if I found the
right project/client/compensation. In the meantime I continue to enjoy
throwing darts at Access and trying to be helpful in this newsgroup.

--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bouncer@localhost.not> wrote in message
news:1PL2e.26605$wL6.5607@trnddc03...[color=blue]
> "Alan Webb" <knogeek@hotmail.com> wrote
>[color=green]
> > . . . I am still bitter, though, because
> > in the job market I competed in knowledge
> > of Access alone wasn't enough to keep me
> > employed. So I tend to trash Access a bit.[/color]
>
> Until the general business climate went South about 2000, in the Dallas -
> Fort Worth area, the problem since 1994 had been finding enough Access
> people to fill the demand for Access developers.
>
> Most of my work was on Access clients to various backend server
> databases -
> Informix, Sybase SQL Anywhere, Sybase and MS SQL Server. But there was a
> good deal of demand, as well, for development of Access apps for
> individuall
> users and Access/Jet multiuser.
>
> There were, of course, areas where I didn't even bother trying to seek
> work -- companies with some server DB who had already decided that the
> client application had to be PowerBuilder, for example. And, it was always
> helpful to have experience in and be skilled in collecting and documenting
> requirements, writing software specs, and designing applications along
> with
> "Access development".
>
> Where are you and what was your target market?
>
> Larry Linson
> Microsoft Access MVP
>
>
>
>[/color]

re: New to Access

RKC,
It's just us noisemakers now. You may be correct. If the list of cars
isn't bigger than 65,000 or so, Excel would probably work almost as well.
--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS
"rkc" <rkc@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:QPF2e.112332$vK5.41126@twister.nyroc.rr.com.. .[color=blue]
> Alan Webb wrote:[color=green]
>> RKC,
>> The [component of] column. Complex bills of materials use at least two
>> tables instead of one. A bill of material is one of the standard schemas
>> for storing hierarchical data. I suggested one table that would use
>> [COMPONENT_OF] to join the table to itself because it is the most
>> straightforward and simple database for a bill of materials. The
>> original poster was not a programmer so one requirement was to keep it
>> simple.[/color]
>
>
> Well, it seems the op isn't really interested so I won't pursue the issue
> except to say that don't see any need for a bill of materials
> to solve the problem. Complex or otherwise.
>[/color]

re: New to Access

Alas, Alan, many of the "darts" you throw at Access just don't make sense,
unless you can't differentiate between Access (the end-user-interface and
development tool) and Jet (the default database engine).

There is no direct comparison between Access and MySQL, for example... one
is a UI tool that can be used with the included Jet database or with any
ODBC compliant database (including MySQL, for the record); the other is a
server database that has to have _some_ kind of front end or client UI.

In this area, the demand for developers seems to be picking up somewhat. The
obsession of the Mighty Microsoft Marketing Machine with huge, enterprise,
distributed, web-based applications and the promotion of .NET has helped the
image of those who develop applications for other environments.

Larry Linson
Microsoft Access MVP


Larry Linson
Microsoft Access MVP





"Alan Webb" <knogeek@hotmail.com> wrote in message
news:HeidnTTxKqrD1dHfRVn-jA@comcast.com...[color=blue]
> Larry,
> I was in the S.F. Bay Area until 2001. These days I am in Richmond, Va.[/color]
and[color=blue]
> in the middle of writing a book on a completely different subject. My
> degree is in English Literature and computers were a hobby that turned[/color]
into[color=blue]
> a career for a while. I'd go back to coding for money again if I found[/color]
the[color=blue]
> right project/client/compensation. In the meantime I continue to enjoy
> throwing darts at Access and trying to be helpful in this newsgroup.
>
> --
> Alan Webb
> knoNOgeek@SPAMhotmail.com
> "It's not IT, it's IS
>
> "Larry Linson" <bouncer@localhost.not> wrote in message
> news:1PL2e.26605$wL6.5607@trnddc03...[color=green]
> > "Alan Webb" <knogeek@hotmail.com> wrote
> >[color=darkred]
> > > . . . I am still bitter, though, because
> > > in the job market I competed in knowledge
> > > of Access alone wasn't enough to keep me
> > > employed. So I tend to trash Access a bit.[/color]
> >
> > Until the general business climate went South about 2000, in the[/color][/color]
Dallas -[color=blue][color=green]
> > Fort Worth area, the problem since 1994 had been finding enough Access
> > people to fill the demand for Access developers.
> >
> > Most of my work was on Access clients to various backend server
> > databases -
> > Informix, Sybase SQL Anywhere, Sybase and MS SQL Server. But there was a
> > good deal of demand, as well, for development of Access apps for
> > individuall
> > users and Access/Jet multiuser.
> >
> > There were, of course, areas where I didn't even bother trying to seek
> > work -- companies with some server DB who had already decided that the
> > client application had to be PowerBuilder, for example. And, it was[/color][/color]
always[color=blue][color=green]
> > helpful to have experience in and be skilled in collecting and[/color][/color]
documenting[color=blue][color=green]
> > requirements, writing software specs, and designing applications along
> > with
> > "Access development".
> >
> > Where are you and what was your target market?
> >
> > Larry Linson
> > Microsoft Access MVP
> >
> >
> >
> >[/color]
>
>[/color]

re: New to Access

I like to get the discussion restarted regarding my original post.
What do I need to do to get started? I responded to Strasser'
question, so what do I do from here

re: New to Access

Larry,
I like Access. I guess I have issues with Jet. There is a longer answer
but it's the wee hours of Saturday morning as I type this and trying to be
lucid at this hour with what I was doing to be awake about now means I
shouldn't pretend to be able to tink clearly. I'll come back to this after
I've had some sleep.
--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bouncer@localhost.not> wrote in message
news:JK_2e.28425$Ax.19157@trnddc04...[color=blue]
> Alas, Alan, many of the "darts" you throw at Access just don't make sense,
> unless you can't differentiate between Access (the end-user-interface and
> development tool) and Jet (the default database engine).[/color]

re: New to Access

Brink,
To get started you need a copy of Access. Create a new Access database.
Inside that database create your first table with column names for the
attributes of the things you want to make a list of. It's probably a good
idea to work with pencil & paper initially to figure out the columns of your
list, what sort of data will be stored in each column, and so on before you
build your table.
--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS"

"brink" <brink@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
news:kqGdnUF28Px2l9DfRVn_vA@giganews.com...[color=blue]
>I like to get the discussion restarted regarding my original post.
> What do I need to do to get started? I responded to Strasser's
> question, so what do I do from here.
>[/color]

re: New to Access

Larry,
It's not so much what is wrong with Jet as it is what I miss from SQL
Server. Triggers, a much better security model, transaction logging and the
ability to recover from the logs, pretty cool support for data cubes, etc.,
are all things that are missing the versions of Jet & Access I own. There
is at least one bit of SQL which was complex enough that Jet wouldn't run it
but SQL Server would. One could make the case that perhaps my SQL was
needlessly complex but with my skillset it was what would get me the result
I wanted. These days I don't do anything with Access & Jet that requires
the things I miss in SQL Server so I just use plain vanilla .mdb's and a bit
of VBA to fill in the gaps where straightforward bound forms and Jet SQL are
not enough. If I work for money again I'd want to use SQL Server or MSDE if
at all possible because security, database triggers, and check constraints
are better suported in these DBMS's.
--
Alan Webb
knoNOgeek@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bouncer@localhost.not> wrote in message
news:JK_2e.28425$Ax.19157@trnddc04...[color=blue]
> Alas, Alan, many of the "darts" you throw at Access just don't make sense,
> unless you can't differentiate between Access (the end-user-interface and
> development tool) and Jet (the default database engine).
>
> There is no direct comparison between Access and MySQL, for example... one
> is a UI tool that can be used with the included Jet database or with any
> ODBC compliant database (including MySQL, for the record); the other is a
> server database that has to have _some_ kind of front end or client UI.
>
> In this area, the demand for developers seems to be picking up somewhat.
> The
> obsession of the Mighty Microsoft Marketing Machine with huge, enterprise,
> distributed, web-based applications and the promotion of .NET has helped
> the
> image of those who develop applications for other environments.
>
> Larry Linson
> Microsoft Access MVP
>
>
> Larry Linson
> Microsoft Access MVP
>
>
>
>
>
> "Alan Webb" <knogeek@hotmail.com> wrote in message
> news:HeidnTTxKqrD1dHfRVn-jA@comcast.com...[color=green]
>> Larry,
>> I was in the S.F. Bay Area until 2001. These days I am in Richmond, Va.[/color]
> and[color=green]
>> in the middle of writing a book on a completely different subject. My
>> degree is in English Literature and computers were a hobby that turned[/color]
> into[color=green]
>> a career for a while. I'd go back to coding for money again if I found[/color]
> the[color=green]
>> right project/client/compensation. In the meantime I continue to enjoy
>> throwing darts at Access and trying to be helpful in this newsgroup.
>>
>> --
>> Alan Webb
>> knoNOgeek@SPAMhotmail.com
>> "It's not IT, it's IS
>>
>> "Larry Linson" <bouncer@localhost.not> wrote in message
>> news:1PL2e.26605$wL6.5607@trnddc03...[color=darkred]
>> > "Alan Webb" <knogeek@hotmail.com> wrote
>> >
>> > > . . . I am still bitter, though, because
>> > > in the job market I competed in knowledge
>> > > of Access alone wasn't enough to keep me
>> > > employed. So I tend to trash Access a bit.
>> >
>> > Until the general business climate went South about 2000, in the[/color][/color]
> Dallas -[color=green][color=darkred]
>> > Fort Worth area, the problem since 1994 had been finding enough Access
>> > people to fill the demand for Access developers.
>> >
>> > Most of my work was on Access clients to various backend server
>> > databases -
>> > Informix, Sybase SQL Anywhere, Sybase and MS SQL Server. But there was
>> > a
>> > good deal of demand, as well, for development of Access apps for
>> > individuall
>> > users and Access/Jet multiuser.
>> >
>> > There were, of course, areas where I didn't even bother trying to seek
>> > work -- companies with some server DB who had already decided that the
>> > client application had to be PowerBuilder, for example. And, it was[/color][/color]
> always[color=green][color=darkred]
>> > helpful to have experience in and be skilled in collecting and[/color][/color]
> documenting[color=green][color=darkred]
>> > requirements, writing software specs, and designing applications along
>> > with
>> > "Access development".
>> >
>> > Where are you and what was your target market?
>> >
>> > Larry Linson
>> > Microsoft Access MVP
>> >
>> >
>> >
>> >[/color]
>>
>>[/color]
>
>[/color]