This topic is locked

Error message when using ASPRunner for an Access query

4/14/2008 10:44:38 AM
ASPRunnerPro General questions
M
mfred author

I attempted to use ASPRunner 5.1 to write a program to read and write to an Access query. But I get an error message when attempting to go past the 'Edit SQL query' screen. The error is at the bottom of this message. I have not edited the SQL query. I went back to version 4 and do not get the error message. Please advise.
Error:

"Cannot retreive columns information. Please modify SQL Query & try again. Error Message: [Microsoft][ODBC Microsoft Access Driver] The SELECT statement includesa reserved work or an argument name that is misspelled, or the punctuation is incorrect."

Admin 4/14/2008

What's the SQL query that causes the issue?

M
mfred author 4/15/2008

It was the ASPRunner default for the table. I went back in to duplicate it and the error is not occuring now, which is wierd since I tried it several times before and got the error each time. The default SQL query was

elect [ID],

[JobNumber],

[F_Name],

[L_Name],

[Email],

[Phone],

[OriginLocation],

[BuildingRoom],

[ProductionLocation],

[ChargeType],

[ChargeCode],

[CustomerReferenceNumber],

[OrderCategory],

[Rush],

[Entry_Date],

[Due_Date],

[Due_Time],

[Status],

[Complete_Date_Time],

[Complete_Time],

[Order_Name],

[Orig_Type],

[PickUpReq],

[Files],

[Proof_Req],

[SFPrint_Job1],

[SFPrint_Job1_Scaling],

[SFPrint_Job1_Sided],

[SFPrint_Job1_Paper],

[SFPrint_Job1_Sets],

[SFPrint_Job1_Orig],

[SFPrint_Job1_StartMeter],

[SFPrint_Job1_Endmeter],

[SFPrint_Job1_MeterCount],

[SFPrint_Job1_Total_Imp],

[SFPrint_Job1_Unit_Price],

[SFPrint_Job1_Subtotal],

[SFPrint_Job1_HCode],

[SFPrint_Job1_MVCode],

[SFPrint_Job1_Type],

[SFPrint_Job2],

[SFPrint_Job2_Scaling],

[SFPrint_Job2_Sided],

[SFPrint_Job2_Paper],

[SFPrint_Job2_Sets],

[SFPrint_Job2_Orig],

[SFPrint_Job2_StartMeter],

[SFPrint_Job2_EndMeter],

[SFPrint_Job2_MeterCount],

[SFPrint_Job2_Total_Imp],

[SFPrint_Job2_Unit_Price],

[SFPrint_Job2_Subtotal],

[SFPrint_Job2_HCode],

[SFPrint_Job2_MVCode],

[SFPrint_Job2_Type],

[LFPrint_Job1],

[LFPrint_Job1_Scaling],

[LFPrint_Job1_Sets],

[LFPrint_Job1_Orig],

[LFPrint_Job1_Size],

[LFPrint_Job1_SqFt],

[LFPrint_Job1_Unit_Price],

[LFPrint_Job1_Subtotal],

[LFPrint_Job1_HCode],

[LFPrint_Job1_MVCode],

[LFPrint_Job1_Type],

[LFPrint_Job2],

[LFPrint_Job2_Scaling],

[LFPrint_Job2_Sets],

[LFPrint_Job2_Orig],

[LFPrint_Job2_Size],

[LFPrint_Job2_SqFt],

[LFPrint_Job2_Unit_Price],

[LFPrint_Job2_Subtotal],

[LFPrint_Job2_HCode],

[LFPrint_Job2_MVCode],

[LFPrint_Job2_Type],

[Tabs],

[Tabs_Sets],

[Num_of_Tabs_Per_Book],

[Tab_Unit_Price],

[Tab_Subtotal],

[Tabs_HCode],

[Tabs_MVCode],

[Binders],

[Binders_Qty],

[Binders_UnitPrice],

[Binders_Subtotal],

[Binders_HCode],

[Binders_MVCode],

[Binding1],

[Binding1_Qty],

[Binding1_UnitPrice],

[Binding1_Subtotal],

[Binding1_HCode],

[Binding1_MVCode],

[Binding2],

[Binding2_Qty],

[Binding2_UnitPrice],

[Binding2_Subtotal],

[Binding2_HCode],

[Binding2_MVCode],

[Covers1],

[Covers1_Qty],

[Covers1_UnitPrice],

[Covers1_Subtotal],

[Covers1_HCode],

[Covers1_MVCode],

[Covers2],

[Covers2_Qty],

[Covers2_UnitPrice],

[Covers2_Subtotal],

[Covers2_HCode],

[Covers2_MVCode],

[Finishing1],

[Finishing1_Qty],

[Finishing1_UnitPrice],

[Finishing1_Subtotal],

[Finishing1_HCode],

[Finishing1_MVCode],

[Finishing2],

[Finishing2_Qty],

[Finishing2_UnitPrice],

[Finishing2_Subtotal],

[Finishing2_HCode],

[Finishing2_MVCode],

[AdditionalLabor1],

[AdditionalLabor1_Minutes],

[AdditionalLabor1_UnitPrice],

[AdditionalLabor1_Subtotal],

[AdditionalLabor1_HCode],

[AdditionalLabor1_MVCode],

[AdditionalLabor2],

[AdditionalLabor2_Minutes],

[AdditionalLabor2_UnitPrice],

[AdditionalLabor2_Subtotal],

[AdditionalLabor2_HCode],

[AdditionalLabor2_MVCode],

[AdditionalCharge],

[AdditionalChargeUnits],

[AdditionalChargeUnitPrice],

[AdditionalChargeSubtotal],

[AdditionalChargeHalCode],

[AdditionalChargeMVCode],

[Job_Subtotal],

[TaxPerc_ExpressedAsDecimal],

[Tax_Subtotal],

[Job_Total],

[Delivery],

[SpecialInstructions],

[InvoiceNumber],

[InvoiceDate]

From [jobQuery01]

Admin 4/16/2008

Even if this query works having 152 fields in single table is a bad idea. Most probably you won't be able to edit data in this table.
You need to reduce number of fields normalizing the data.