Okay then, some (small) amount of progress. I've got the SQL log, which doesn't help that much.
However, restricting the report to just one or two fields rather than all allows the query/extract to run correctly. Nothing in the logs points to which field is causing the report to crash out, so is there any option other than trial and error for determining which field is at fault? I've tried copying a bunch of the various query lines into the SQL query analyser, they all parse correctly and run fine, from the initial *SELECT T2062.C1,T2062.C1,C536871272 FROM T2062 ORDER BY 3 ASC* to the *SELECT C1,C536870926,C536870921,C536870928,C536870924,C536870931,C536870933,C536870993,C536871291,C536871290,C536871303,C536871304,C536871008,C536871240,C536871241,C536871267,C536871297,C536871233,C536870991,C536871286,C536871302,C536870945,C536871239,C536870937,C536870964,C536871284,C536870961,C536870965,C536871419,C536871418,C536870969,C536870966,C536870967,C536870968,C536871310,C536871299,C536871273,C536871272,C536871342,C536870922,C536870929,C536871019,C536870919,C536870925,C536870932,C536871279,C536871288,C536870915,C536870914,C536870913,C536870917,C1,C536871298,C536871155,C536871285,C7,C536871293,C536871017,C536870962,C536870954,C536870963,C536870956 FROM T2062 WHERE (E0 = '000000000000251' and E1 IS NULL )* So maybe we've just got one record that is throwing things out? Regards Dave On 01/12/06, Carey Matthew Black <[EMAIL PROTECTED]> wrote:
Dave, This is a WAG without seeing the SQL in question... but... I would make sure that the user is using the following procedure. 1) Open form in Query mode. 2) Specify search conditions 3) DO NOT DO THE SEARCH 4) Jump directly to the report selection screen from the QUERY window. 5) select the report in question. 6) Extract the data. Because there can be "issues" when the user use the following procedure: 1) Open form in Query mode. 2) Specify search conditions 3*) DO THE SEARCH 4*) Select some set of record from the Results list or none 5) Open the report selection screen from the MODIFY window. 6) select the report in question. 7) Extract the data. The details (of why it matters) have to to with the query that is passed to the DB. When the Query is the Search conditions it is normally much shorter than the query passed when it is a list of selected (or already returned) 'Entry ID' values. HTH -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 12/1/06, Dave Barber <[EMAIL PROTECTED]> wrote: > ** > All, > > One of our users is running a report/extract against a join form. You can > browse the join form without any issues, but upon running the report and > extracing the data, you get the following : > > Error occurred in generating report. > ARERR [552] failure during SQL operation to the database : Line 1; Incorrect > syntax near ')' (SQL Server 170). > > From what I've browsed, that seems to imply that we have a field with a > label of ')'. The only field labeled with a non-text character is labelled > with a dash (-). Its not this field thats throwing out the extract (removal > of it still leaves the same issue). > > Its an in-house application, running on ARS 5.1.2 against a SQL Server > database. > > Any suggestions? > > Regards > > Dave _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
