Help, no table.

[Ted Clore]

I created a Form with about a 175 Fields. Some of the Fields are linked to various tables where I get information such as customer, or employee. But it won't let me save it as a record and I can't add any records. I think it is because there is no table for this form. Is there a way to create a table form a form?

Thanks,
Ted

 

[BruceM]

Without knowing more about your design it is difficult to comment. What is
the purpose of the database? Why do you need Customer and Employee in the
same record? I'm not questioning that you do, but there are quite a few
possible scenarios.
Database design starts with tables and relationships. You need those to
work before you can start thinking about forms.
By the way, if you are using HTML format for messages to the group you would
probably do best to change to plain text.

I created a Form with about a 175 Fields. Some of the Fields are linked to
various tables where I get information such as customer, or employee. But
it won't let me save it as a record and I can't add any records. I think it
is because there is no table for this form. Is there a way to create a
table form a form?

Thanks,
Ted

 

[Lynn Trapp]

Ted,
How are some of your " Fields linked to various tables" if there is not
table or query as the record source for your form?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I created a Form with about a 175 Fields. Some of the Fields are linked to
various tables where I get information such as customer, or employee. But
it won't let me save it as a record and I can't add any records. I think it
is because there is no table for this form. Is there a way to create a
table form a form?

Thanks,
Ted

 

[Ted Clore]

I am trying to tie in some information into a single form for convenience.
I work in a job shop and it is important to track jobs by some criteria.

I need to know:

1) Customer, Part #, Quantities, descriptions

and then tie that into

2) Employee times and processes

And then tie that into

3) Vendors and costs of Outside Labor and Materials purchased.

Then I use some formula's to calculate, an hourly rate and a per piece cost
of the parts.

So far I have a table for, Employees, Customers, Vendors and Processes.
We track the job's by sequential job #'s and need to refer back to the job's
when someone orders from us again. So what I am trying to accomplish is a
way to look up a part number, and see the information about what went into
that part or look up a job number and see how we did on a particular job or
look up a customer and see our sales to a customer. Also, the owner wants
to look at the job's when the job is complete to see how the job did
according to the quotes that we bid on an hourly basis. Since we are a job
shop, and we make a wide variety of "stuff", the part #'s are not
necessarily our part #'s, and may only process through the shop one time.
But it is still vital for our process to look up a job and see the hourly
rate.

Also, Thanks for the tips. Sorry I sent the last response to your email
address.

Ted

 

[Ted Clore]

Links are by a combo box, which looks up a row source from a Table.

Forgive me if I don't speak Access-ese, this is all new to me.

I am thinking I should start over, and establish tables for all of the data
I want. My problem is that I am not sure how to store data from a source
like Employee, Process, date and Hours worked. This may occur one time or a
hundred times on a particular job and I need to see totals of that
information, plus I need to see it listed out.

My goal is to have a job record of each job that comes into the shop and
have certain information available for various persons in the shop.

Thank you Lynn. Sorry I sent the last response to your email address.

 

[PC Datasheet]

Ted,

If you would want some outsude help from just designing the tables the whole
way to creating the database for you, send me an email to my emasil address
below.

 

[John Vinson]

Is there a way to create a table form a form?

You are working backwards.

A Form isn't a data storage medium; it's a tool, a window for viewing
and editing data. Your Tables are the foundation of your building; the
forms are part of the structure, like windows in the house. Nobody
starts a house by assembling the windowframes and then deciding where
to pour the foundations!

Stop, step back, and do some reading; or look at the Northwind sample
database. You don't want to create a jumble of fields (175 is a HUGE
number of fields...) on a form and then figure out where to put them;
instead, you start with a properly normalized set of Tables (with a
small number of fields per table, no more than 25 at the most), and
use Forms, Subforms, comboboxes and other tools to interact with the
data in these tables.

John W. Vinson[MVP]

 

[BruceM]

I see that this thread has been picked up by others, so I will bow out of
this part of the thread and track your progress in the other threads,
jumping in if I can help. John Vinson's observations are particularly apt.
You have embarked on quite a project for somebody new to Access. If you are
in a hurry you may need to resort to outside help, although if I were you I
would not jump on the first offer that shows up. If you have some time, do
as John suggests. There are plenty of resources that will allow you to
develop your own project.
It sounds as if Job # will be the first level of your database, and that
Employees, Vendors, and all of the time and expenses particular to that job
will need to be linked to it. Do you do something like perform value-added
services (machining, heat-treating, or something) on customer parts? If you
do that, do you do something else as well with manufacturing your own parts?
These sorts of things could be described when you post a reply.
Again, please pick this up in another part of the thread (John Vinson's
would be good), so that the conversation can remain linear rather than
scattered around several postings.

 

[StopThisAdvertising]

I am still watching you Steve ... (and so are others ...)

You are behaving much better recently but you are (again) trying again so ...

please Steve, stop jobhunting here...
****************************

There is NO justification to do so , you should know that by now.
We don't want to go 'all over it' again ?

Arno R

 

[PC Datasheet]

See BruceM's post --

"You have embarked on quite a project for somebody new to Access. If you
are
in a hurry you may need to resort to outside help ..."\

.... (and so are others ...)
You don't know this! Your just a liar! All you're trying to do is cause
trouble again. Just bug-off!!!


--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
(e-mail address removed)
www.pcdatasheet.com


I am still watching you Steve ... (and so are others ...)

You are behaving much better recently but you are (again) trying again so
....

please Steve, stop jobhunting here...
****************************

There is NO justification to do so , you should know that by now.
We don't want to go 'all over it' again ?

Arno R

 

[BruceM]

I also said that I wouldn't jump at the first offer that showed up. As it
happens, that was yours. I only made that comment after seeing your offer.
I have seen several instances in these groups where a questioner has
solicited offers for consulting help, but this wasn't one of those. I am
one of the "others" who noticed, and did not think highly of your promoting
your paid services in this forum.
That is all I will say on this point. I do not wish to be drawn into
controversy, but need to say I would rather you not use a selective quote
from me to bolster your position.

 

[Ted Clore]

Thank you John,

I will do as you said and look at the examples, although I find them a bit
confusing if I try and relate them to my application. What I will do is
build the database like I want it and then upload it to the group for
criticism and suggestions to better the designs, if that is alright. I have
trimmed some of the fields and ended up with about 145.

Thanks again,
Ted

 

[John Vinson]

Thank you John,

I will do as you said and look at the examples, although I find them a bit
confusing if I try and relate them to my application. What I will do is
build the database like I want it and then upload it to the group for
criticism and suggestions to better the designs, if that is alright. I have
trimmed some of the fields and ended up with about 145.

Ummm... No. Please DON'T.

This is a text-only newsgroup. Uploading databases (or other binary
attachments) is NOT acceptable. If someone *volunteers* (perhaps in
response to a request) to look at it, you can Zip it and EMail it to
that person - but please don't post it here.

Again - if you have 145 fields in a table, *that's ten times too
many*. Read the links elsewhere in this thread about "normalization";
if you have repeating fields in your table (such as January, February,
.... or Field1, Field2, Field3, ...) then your table needs to be split
into two tables in a one-to-many relationship.

If you wish, you can post a *TEXT* description of your tables, with
the table names, the Primary Keys (specify the datatype), the defined
relationships, and perhaps a sampling of the fields within the tables.


John W. Vinson[MVP]