Database Design

[Bob Foster]

Hello to all,
I have limited access experience but still need to forge ahead. The
application I would like to build works like this. I work in a machine shop
environment and have an issue keeping prints, work instruction, programs and
other data in manner that is convenient for accessibility. I would like to
build a database where I can store all this info in one place. This could
either work by linking to the data or storing it in the database itself. CNC
Programs that we use for machining have to be transferred from the PC to the
machine tool via serial communications. I would like to have the ability to
transfer these programs from within the database. Also, I would most
definitely like to store these programs in the database with the ability keep
a history with these programs as well. Basically each time a program is
re-written I would like to archive the old program in its original state then
add the new one. The new program would be the only program that could be used
by a person with shop level security clearance. Keeping copies of the prints
and work instructions in the same matter would be preferred as well but not
completely essential. Making sure I always have to most current information
available is the goal at completion.
One other thing I would like to accomplish would be to have the ability to
lock out a particular program if it is in transition. This would be programs
that are in the middle of an engineering change.
I think that is enough info to generate a lot of questions for now
I'm looking forward to hearing from you and certainly appreciate all your
input.
Thanks,
Bob

 

[Jeff Boyce]

Bob

It sounds like you have a good grasp of what you are looking to achieve (or
acquire). You've described much of the functionality you seek.

You'll probably find these newsgroups much more useful if you post a
specific question. Many of the folks who post & respond here already have
full-time jobs and/or consulting businesses, so they'll be much more likely
to have the time to respond to something specific than to a general outline.

I don't see a specific question in your post...

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/

 

[Bob Foster]

Hmm. You're right. I guess my question is this. What I discribed is an
application I would like to build. Are all the things I am looking for in
this application capable in Access? Storing these programs In ASCII format.
Serial Communications? Storing PDF files, Cad Files, ect..ect.. I guess if
they are all possible, where would be a good place to start gathering data on
how to get started? Any books that someone might reccomend? Will I need to
become versed in Visual Basic to achieve this. I'm sure I can come here for
the hard questions but would not want to tie up this forum to achieve the
entire project.
Hope this clears it up a little.
-Bob

 

[Jeff Boyce]

Bob

If you have only limited experience with Access, you will find the learning
curve fairly steep. Doing simple things is easy. Making an application
"user-proof" is much more difficult.

It sounds a little like you are working with version control, or
configuration management. Have you tried looking into some of the COTS
(commercial, off-the-shelf) packages that do this?

This forum and the I'net is fairly robust ... I don't think you would "tie
it up", but I do think that it is purposed more for helping with specific
questions than for an overall development project.

--
Regards

Jeff Boyce
Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

Microsoft Registered Partner
https://partner.microsoft.com/

 

[mnature]

I was able to find a few canned programs for machine shops. These have demos
available.

http://www.kentechinc.com/index.shtml

http://www.ksitech.com/home.html

Creating your own database is a daunting task which can be very rewarding,
but can also take a lot of time. If you are attempting this simply because
someone mentioned that Access is an easy way to make a database, then you
might want to seriously consider purchasing software. If you have always
wanted to learn how to program in Access, then you have chosen a very complex
first project.

The first step in creating a database is to determine exactly what elements
will go into it. Much of what you are describing is what you want to do with
those elements. There are a number of "Idiot's Guide"-type books about
Access, which are good for just getting your feet wet. For guides on
database design, I would recommend Hernandez' book, Database Design for Mere
Mortals (now in 2nd edition), and O'Reilly's Access Database Design &
Programming. The one main reference book (and I emphasize that it is for
reference) would be Microsoft Office Access 2003 Inside Out.

The job of creating coherent normalized tables is an essential first step
towards creating a viable database. You cannot skip this step, nor can you
take short-cuts with it.

 

[Bob Foster]

Thanks for your input Jeff, Point taken. I have developed databases in the
past during the early days in DOS with a relational database program called
DataEase. It was a fairly complex scheduling system that worked well but
nothing like I am thinking about with Access and this new app. I have looked
into many off the shelf systems but there expensive and rairly have
everything you need. Hence the reason there are forum's like this to help
people learn and create applications that fit there specific needs. I will
forge ahead and see what kind of issues arise. At least I know where to come
if I get in trouble.
Thanks again,
-Bob

 

[Bob Foster]

First of all, thanks for the links to the software. Especially KSI, I was
unaware of there presence. I appreciate your input and consider some of the
books you mentioned. I look forward to this cahllenge. If you read the post I
left for Jeff above you'll see I have some Relational database experience for
years back but Access will be a new challenge. I will consider your
suggestions as I forge ahead in this project.
Thanks Again,
-Bob