InfoPath Dev

 I am getting an error on the Order By clause.  Does anyone know the correct syntax?   command += "{select * "; command += "from "; command += "[LaborSummary] as [LaborSummary] "; command += "where (LaborSummary.[CA1] = '" + ca1Prefix + "')} "; command += ...

That worked great!  Thanks   Now what about the Order By clause?  I get an error with the below code on the Order By clause.    command += "{select * "; command += "from "; command += "[LaborSummary] as [LaborSummary] "; command += "where (LaborSummary.[CA1] = '" + ...

 Does anyone know how to use the where clause with the shape clause? I get a error on the following code at the Where clause....     command += "{select "; command += "[CA1],[HOUR_DOLLAR],[DIST_NONDIST],[MASTER],";  command += ...

I have a Expression Box that I want to change the font color to red if less than or equal to -1.  I thought I had seen on another form with an Conditional Formating option an that read "Sum of Expression Box"  but I do not see on my current form. How can I check for the Sum in an expression box so I can control the font color?

LaborSummary Autonumber(Primary Key) CA xxx xxx     LaborSummaryCommentsLabor    Autonumber(Primary Key)    CA_L    Comments   I have a CA to CA_L relationship setup between the two tables...which will  be a  one to many.  

I setup my tables and relationships like stated above but get the following error when I create the Data Connection:    A many to one relationship might exist between two tables in the form What am I doing wrong?

My field in Access is setup as a type "double" with 4 decimal places.  When I perform a "sum" function on that column I get the 1QNAN error anytime I have a number after the decimal point such as 0.0025.  The sum works fine if all the columns something like  0.0000 or 1.2500.   ...

I have a another quick question...I am summing a field set as Decimal with 4 places such a 0.0000.  Some records have 0.0000 and others have numbers such as 812.1677.  I get 1#QNAN sometimes even though there are no blanks in the field.  Do you know why?

So the child tables do not have to have a record associated with a record on the parent table to start?  I want a one to may relationship where there are no comments to start and users can add as many comments as they want to per Control Account.

This may be my problem...I am using the ID and MainID as the same key on the child table...for the table and for the link to the parent table. ID  Name  Decription    etc 1    Test     Testing        x 2    Test2    Test ...