>-----Original Message-----
>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT
MODEL
>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE
POINT,
>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  I
>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS DESIGNED
>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY TO
>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO ABOUT
>DOING THIS?  

>I HAVE TRIED THE ACTION QUERY MAKE-TABLE.  BUT THAT GAVE
>ME A BLANK SUBFORM.  I HAVE ALSO MADE CERTAIN MY
>RELATIONSHIPS ARE SET UP PROPERLY. I HAVE A JOIN PROPERTY
>OF "1" FOR THE RELATIONSHIP IN THE QUERY THAT THE SUBFORM
>USES.  THIS IS A ONE-MANY RELATIONSHIP.  THE CUSTOMERID
>CAN PURCHASES MORE THAN ONE PIECE OF EQUIPMENT.

>THANK YOU FOR ANY HELP!
>.

>-----Original Message-----
>Interesting, I have somewhat of the same problem.  I have
>a Form(PO)that has a sub form(PO items or PartsID) that
>part of the sub form is based on a query.  Some field are
>updateble, Some are not.  The field that are unupdateable
>are the field that are unbound and not part of the query.

>>-----Original Message-----
>>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT
>MODEL
>>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE
>POINT,
>>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  
I
>>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS
DESIGNED
>>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY
TO
>>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO ABOUT
>>DOING THIS?  

>>I HAVE TRIED THE ACTION QUERY MAKE-TABLE.  BUT THAT GAVE
>>ME A BLANK SUBFORM.  I HAVE ALSO MADE CERTAIN MY
>>RELATIONSHIPS ARE SET UP PROPERLY. I HAVE A JOIN
PROPERTY
>>OF "1" FOR THE RELATIONSHIP IN THE QUERY THAT THE
SUBFORM
>>USES.  THIS IS A ONE-MANY RELATIONSHIP.  THE CUSTOMERID
>>CAN PURCHASES MORE THAN ONE PIECE OF EQUIPMENT.

>>THANK YOU FOR ANY HELP!
>>.

>.

>-----Original Message-----
>I HAVE THAT PROBLEM AS WELL.  I FEEL THAT IS BECAUSE THE
>FIELDS THAT ARE UPDATING ARE IN THE QUERY.  THE SAME
>FIELDS IN THE TABLE ARE BLANK.  I WOULD LIKE THOSE SAME
>FIELDS IN THE TABLE TO UPDATE WHEN THE QUERY UPDATES.  
>THAT I DON'T KNOW HOW TO DO, AS OF YET.  

>MY PROBLEM WITH THE SUBFORM NOT ALLOWING NEW RECORDS I
>KNOW STEMS FROM SOMETHING IN THE QUERY.  WHENEVER I HAVE
A
>SMALL GLITCH IN THE DATABASES PERFORMANCE, THE SOLUTION
>RESIDES IN THE QUERY,OR EVEN SOMETHING PETTY AS A
PROPERTY
>SETTING.

>IF SOMEONE WHO IS MORE VERSED COULD HELP WITH THESE
>SIMILAR PROBLEMS THAT WOULD BE APPRECIATED!

>>-----Original Message-----
>>Interesting, I have somewhat of the same problem.  I
have
>>a Form(PO)that has a sub form(PO items or PartsID) that
>>part of the sub form is based on a query.  Some field
are
>>updateble, Some are not.  The field that are
unupdateable
>>are the field that are unbound and not part of the query.

>>>-----Original Message-----
>>>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>>>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT
>>MODEL
>>>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>>>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE
>>POINT,
>>>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  
>I
>>>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>>>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>>>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>>>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>>>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS
>DESIGNED
>>>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY
>TO
>>>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>>>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO
ABOUT
>>>DOING THIS?  

>>>I HAVE TRIED THE ACTION QUERY MAKE-TABLE.  BUT THAT
GAVE
>>>ME A BLANK SUBFORM.  I HAVE ALSO MADE CERTAIN MY
>>>RELATIONSHIPS ARE SET UP PROPERLY. I HAVE A JOIN
>PROPERTY
>>>OF "1" FOR THE RELATIONSHIP IN THE QUERY THAT THE
>SUBFORM
>>>USES.  THIS IS A ONE-MANY RELATIONSHIP.  THE CUSTOMERID
>>>CAN PURCHASES MORE THAN ONE PIECE OF EQUIPMENT.

>>>THANK YOU FOR ANY HELP!
>>>.

>>.

>.

>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT MODEL
>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE POINT,
>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  I
>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS DESIGNED
>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY TO
>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO ABOUT
>DOING THIS?  

>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT MODEL
>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE POINT,
>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  I
>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS DESIGNED
>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY TO
>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO ABOUT
>DOING THIS?  

>I HAVE TRIED THE ACTION QUERY MAKE-TABLE.  BUT THAT GAVE
>ME A BLANK SUBFORM.  I HAVE ALSO MADE CERTAIN MY
>RELATIONSHIPS ARE SET UP PROPERLY. I HAVE A JOIN PROPERTY
>OF "1" FOR THE RELATIONSHIP IN THE QUERY THAT THE SUBFORM
>USES.  THIS IS A ONE-MANY RELATIONSHIP.  THE CUSTOMERID
>CAN PURCHASES MORE THAN ONE PIECE OF EQUIPMENT.

>THANK YOU FOR ANY HELP!

>-----Original Message-----
>On Mon, 21 Apr 2003 08:13:38 -0700, "DAND"

>>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT
MODEL
>>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE
POINT,
>>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  
I
>>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS
DESIGNED
>>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY
TO
>>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO ABOUT
>>DOING THIS?  

>First off... please lay off the CAPS LOCK KEY. It makes
your messages
>very much harder to read, and looks like you're SHOUTING
AT US. If
>using the shift key is awkward, it's preferable to type
in all lower
>case.

>The Query that you're using as the basis for the form
probably is not
>updateable. Queries *do* work for forms - I use them all
the time -
>but it must be an updateable query. There are many
reasons why a query
>might not be updateable; the most common is that you must
have a
>unique index, such as a Primary Key, on the joining field
on the "one"
>side of the relationship, and you must have Enforce
Relational
>Integrity checked on the relationship properties. It
makes no
>difference whether you choose 1, 2, or 3 as the

>this purpose.

>If this doesn't help, please open the query in SQL view
and post the
>SQL text here.

>                  John W. Vinson[MVP]    
>    Come for live chats every Tuesday and Thursday
>http://go.compuserve.com/msdevapps?loc=us&access=public
>.

>SELECT Count(pi.PartInstanceID) AS PartCount, pi.PartID AS
>PartID, pi.PartCost AS PartCost, pi.OrderID AS OrderId,
>(select count(partinstanceid) from tblpartinstance where
>partlocation <> 8 and orderid =  pi.[OrderID] and partid =
>pi.[PartID]) AS ReceivedCount, (select count
>(partinstanceid) from tblpartinstance where partlocation =
>8 and orderid =  pi.[OrderID] and partid = pi.[PartID]) AS
>CancelledCount, tblLocation.Location
>FROM tblPartInstance AS pi, tblLocation
>GROUP BY pi.PartID, pi.PartCost, pi.OrderID,
>tblLocation.Location;

>>-----Original Message-----
>>On Mon, 21 Apr 2003 08:13:38 -0700, "DAND"

>>>I HAVE A SUBFORM THAT IS USES A QUERY THAT LOOKS UP ALL
>>>THE COMPONENTS FOR ONE FIELD. I.E., SELECT EQUIPMENT
>MODEL
>>>NUMBER AND THE PRICE, ETC. FIELDS FILL IN.  THIS WORKS
>>>PERFECTLY.  I WAS ABLE TO ENTER A NEW RECORD AT ONE
>POINT,
>>>BUT NOW I AM NOT ABLE TO.  THE SUBFORM WON'T ALLOW IT.  
>I
>>>HAVE CHECKED THE PROPERTIES AND THEY DO ALLOW ADDTIONS,
>>>DELETIONS, ETC. I DO KNOW FROM EXPERIENCE THAT A
>>>FORM/SUBFORM WORKS BETTER WHEN A TABLE IS THE
>>>RECORDSOURCE.  ON THE SUBFORM I AM USING A QUERY.  THE
>>>QUERY CONSISTS OF A TABLE AND THE QUERY THAT WAS
>DESIGNED
>>>TO LOOKUP THE EQUIPMENT MODEL NUMBER.  IF THE ONLY WAY
>TO
>>>ADD NEW RECORDS IS TO USE A TABLE, PROBABLY SO THAT ALL
>>>THE RECORDS HAVE A PLACE TO BE STORED, HOW DO I GO ABOUT
>>>DOING THIS?  

>>First off... please lay off the CAPS LOCK KEY. It makes
>your messages
>>very much harder to read, and looks like you're SHOUTING
>AT US. If
>>using the shift key is awkward, it's preferable to type
>in all lower
>>case.

>>The Query that you're using as the basis for the form
>probably is not
>>updateable. Queries *do* work for forms - I use them all
>the time -
>>but it must be an updateable query. There are many
>reasons why a query
>>might not be updateable; the most common is that you must
>have a
>>unique index, such as a Primary Key, on the joining field
>on the "one"
>>side of the relationship, and you must have Enforce
>Relational
>>Integrity checked on the relationship properties. It
>makes no
>>difference whether you choose 1, 2, or 3 as the
>relationship type for
>>this purpose.

>>If this doesn't help, please open the query in SQL view
>and post the
>>SQL text here.

>>                  John W. Vinson[MVP]    
>>    Come for live chats every Tuesday and Thursday
>>http://go.compuserve.com/msdevapps?loc=us&access=public
>>.

>SELECT Count(pi.PartInstanceID) AS PartCount