parameter query and making a new record

[WindandWater]

Sorry for such a basic question, but I have looked in several books
and online for this simple question.

What are the commands to create a new record and append
some data by using a parameter query? The field I want to
call input on is jobNumber. If there is a better way than using
parameter query, I would really like to know.

One more note, I have a situation in my database where I have
a need to have more than one form page to enter my data in
correctly....So, I am trying to avoid two forms and and some
redundant data entry.

I want to use my
existing fields for the following table:

tblJobs

fields type size
jobNumber text 10
catCode text 10
jobStatusID number long int
plaPackageID number long int
jobID autonumber
failureFrequency Yes/no
approved yes/no
quicksheetID number long Int

 

[John W. Vinson]

Sorry for such a basic question, but I have looked in several books
and online for this simple question.

What are the commands to create a new record and append
some data by using a parameter query? The field I want to
call input on is jobNumber. If there is a better way than using
parameter query, I would really like to know.

One more note, I have a situation in my database where I have
a need to have more than one form page to enter my data in
correctly....So, I am trying to avoid two forms and and some
redundant data entry.

I want to use my
existing fields for the following table:

tblJobs

fields type size
jobNumber text 10
catCode text 10
jobStatusID number long int
plaPackageID number long int
jobID autonumber
failureFrequency Yes/no
approved yes/no
quicksheetID number long Int

Where are you appending FROM? Just what do you mean by "call input on"? If you
want the user to simply enter new data directly you don't need a query at all.

If you need more space on the screen than one form will provide consider using
a Tab Control on the form. It's an area of screen with two or more tabs (like
file folder tabs) along the edge, that lets you put multiple controls on each
page. However, if you have more fields in a table than will fit on a normal
size screen, you very likely have an incorrectly structured table; what are
you trying to enter?

 

[WindandWater]

Hello John,

I think I should back up and explain my database. What I have is a trouble
ticket system, (quicksheets) and there are jobs for some of the quicksheets.
Jobs are the funding that fix the trouble tickets, based on priorities set on
the quicksheets.
There is a one to many releationship, where jobs is on the one side.

The quicksheets table is also in other one to many releationships, where it
is on the one side of the relationship. This is with tables like facilities
and systems.

I need a way to create quicksheets, but sometimes I have a job related to
the quicksheet.

I have been successful in setting up to seperate forms for data entry.

I just wonder if I can make it into one form with out too much coding?

Thank you,

Johnny

 

[John W. Vinson]

Hello John,

I think I should back up and explain my database. What I have is a trouble
ticket system, (quicksheets) and there are jobs for some of the quicksheets.
Jobs are the funding that fix the trouble tickets, based on priorities set on
the quicksheets.
There is a one to many releationship, where jobs is on the one side.

The quicksheets table is also in other one to many releationships, where it
is on the one side of the relationship. This is with tables like facilities
and systems.

I need a way to create quicksheets, but sometimes I have a job related to
the quicksheet.

I have been successful in setting up to seperate forms for data entry.

I just wonder if I can make it into one form with out too much coding?

I would expect so; a form can have multiple subforms, and subforms can have
subforms. The problem here is that you have a one (jobs) to many (quicksheets)
relationship, but it's not an enforced, "real" relationship since you can
apparently have quicksheets which do not relate to any job.

Might it be possible to have a "dummy" Jobs record, a default job which
applies to all quicksheets that don't otherwise have a job? This would make it
possible to use a Form based on the jobs table, with a Subform for
quicksheets, and sub-subforms for the facilities and systems.

No code or queries would be needed with this construction.

 

[WindandWater]

Hello John,

This form design is simpler, but the order which data is entered might
cause some issues. I have set up a "dummy job" which by a default
value all quicksheets are assinged to.

The issue in my testing is that quicksheets will mainly get populated first.
The funding of the quicksheets is by the job, which comes afterward.
So, when I go to create a new job I get a blank quicksheet record.
This is opposite of how it would really be.

I then populated some quicksheet tickets, which all by default are associated
to the "dummy job". Now when I want to create a job I get a blank quicksheet.

I am thinking if I can get my append query to work, I will be in buisness....