473,320 Members | 1,838 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

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

Nov 13 '05 #1
21 1840
brink wrote:
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.


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

Nov 13 '05 #2
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.
Nov 13 '05 #3
That said... read this...

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

Nov 13 '05 #4
Pietlinden,
Cool.

<pi********@hotmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
That said... read this...

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

Nov 13 '05 #5
ng
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" <br***@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
news:2a********************@giganews.com...
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.

Nov 13 '05 #6
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS
"ng" <ng@ng.com> wrote in message news:4y_1e.34386$oa6.8454@trnddc07...
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" <br***@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
news:2a********************@giganews.com...
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.


Nov 13 '05 #7
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..

Nov 13 '05 #8
"Alan Webb" wrote
Access isn't really for folks that
studied databases and programming in
college.
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.)
On the cheap, PostgreSQL & a decent
open source Java IDE like Eclipse are
probably better.
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.
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.
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 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
kn*******@SPAMhotmail.com
"It's not IT, it's IS
"ng" <ng@ng.com> wrote in message news:4y_1e.34386$oa6.8454@trnddc07...
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" <br***@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
news:2a********************@giganews.com...
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.



Nov 13 '05 #9
rkc
Alan Webb wrote:
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


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?

Nov 13 '05 #10
rkc wrote:
How about the 2003 Ford Explorer?


Ford. At least they circled the problem :-)

--
[Oo=w=oO]

Nov 13 '05 #11
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS
"Larry Linson" <bo*****@localhost.not> wrote in message
news:74i2e.28245$b_6.16115@trnddc01...

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.)

Nov 13 '05 #12
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS

"rkc" <rk*@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:m3********************@twister.nyroc.rr.com.. .

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?

Nov 13 '05 #13
rkc
Alan Webb wrote:
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.

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.

Nov 13 '05 #14
"Alan Webb" <kn*****@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 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


Nov 13 '05 #15
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bo*****@localhost.not> wrote in message
news:1PL2e.26605$wL6.5607@trnddc03...
"Alan Webb" <kn*****@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 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

Nov 13 '05 #16
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS
"rkc" <rk*@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:QP********************@twister.nyroc.rr.com.. .
Alan Webb wrote:
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.

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.

Nov 13 '05 #17
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" <kn*****@hotmail.com> wrote in message
news:He********************@comcast.com...
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bo*****@localhost.not> wrote in message
news:1PL2e.26605$wL6.5607@trnddc03...
"Alan Webb" <kn*****@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 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


Nov 13 '05 #18
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

Nov 13 '05 #19
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bo*****@localhost.not> wrote in message
news:JK_2e.28425$Ax.19157@trnddc04...
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).

Nov 13 '05 #20
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS"

"brink" <br***@mygalaxyexpress-dot-com.no-spam.invalid> wrote in message
news:kq********************@giganews.com...
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.

Nov 13 '05 #21
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bo*****@localhost.not> wrote in message
news:JK_2e.28425$Ax.19157@trnddc04...
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" <kn*****@hotmail.com> wrote in message
news:He********************@comcast.com...
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
kn*******@SPAMhotmail.com
"It's not IT, it's IS

"Larry Linson" <bo*****@localhost.not> wrote in message
news:1PL2e.26605$wL6.5607@trnddc03...
> "Alan Webb" <kn*****@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 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
>
>
>
>



Nov 13 '05 #22

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

63
by: Jerome | last post by:
Hi, I'm a bit confused ... when would I rather write an database application using MS Access and Visual Basic and when (and why) would I rather write it using Visual Studio .Net? Is it as easy...
13
by: bill | last post by:
I am trying to convince a client that dotNet is preferable to an Access project (ADP/ADE). This client currently has a large, pure Access MDB solution with 30+ users, which needs to be upgraded....
1
by: Dave | last post by:
Hello NG, Regarding access-declarations and member using-declarations as used to change the access level of an inherited base member... Two things need to be considered when determining an...
13
by: Simon Bailey | last post by:
I am a newcomer to databases and am not sure which DBMS to use. I have a very simplified knowledge of databases overall. I would very much appreciate a (simplifed) message explaining the advantages...
0
by: Frederick Noronha \(FN\) | last post by:
---------- Forwarded message ---------- Solutions to Everyday User Interface and Programming Problems O'Reilly Releases "Access Cookbook, Second Edition" Sebastopol, CA--Neither reference book...
20
by: Olav.NET | last post by:
I am a .NET/C++ developer who is supposed to do some work with Access. I do not know much about it except for the DB part. Questions: *1* I am looking for INTENSIVE books to get quickly up to...
64
by: John | last post by:
Hi What future does access have after the release of vs 2005/sql 2005? MS doesn't seem to have done anything major with access lately and presumably hoping that everyone migrates to vs/sql. ...
1
by: com | last post by:
Extreme Web Reports 2005 - Soft30.com The wizard scans the specified MS Access database and records information such as report names, parameters and subqueries. ......
17
by: Mell via AccessMonster.com | last post by:
Is there a way to find out where an application was created from? i.e. - work or home i.e. - if application sits on a (work) server/network, the IT people know the application is sitting...
37
by: jasmith | last post by:
How will Access fair in a year? Two years? .... The new version of Access seems to service non programmers as a wizard interface to quickly create databases via a fancy wizard. Furthermore, why...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
0
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.