cgosbee
Posts: 23
|
| Posted: 10/12/2007, 7:05 PM |
|
I have a maintenance form that HAD a Custom Insert. I wasn't having any luck with getting my Custom Insert to do what I needed, so I decided to rely on triggers instead.
At first, I left it as a Custom Insert Type of Table, simply removing the fields that could be populated on insert by a trigger.
The INSERT (which was working previously, except I couldn't get one of the fields to update properly) now fails, because the automatically generated query has extraneous commas where the old fields/columns would have been in the SQL Insert.
Since that didn't work, I cleared the "Custom Insert Type" and "Custom Insert" fields altogether, hoping it would return to a straight non-custom insert, and tried that... I get the same result.
Nothing I do with those custom queries seems to make any difference (in fact, I have tried adding fields in, and it continues to always have an extraneous comma no matter what I do)
An example of what it is doing: "INSERT INTO table (fld1, fld2, fld3, ) VALUES (1,2,3,4)"
Does anyone have any idea where the source of problem is likely to be? (Generating PHP, if that matters at all.)
|
 |
 |
wkempees
Posts: 1679
|
| Posted: 10/14/2007, 6:13 AM |
|
If the page/form itself is not to complicated to build, than the fastest way to evercome this is to delete the page and build it new.
This will take you 5 minutes, solviong the problem might take days?
Walter
PS your sql example in itself has a comma too many in the fields part.
_________________
Origin: NL, T:GMT+1 (Forumtime +9)
CCS3/4.01.006 PhP, MySQL .Net/InMotion(Vista/XP, XAMPP)
if you liked this info PAYPAL me: http://donate.consultair.eu
|
|
|
|
cgosbee
Posts: 23
|
| Posted: 10/15/2007, 11:17 AM |
|
Thanks, I suspected that was the case.
|
|
|
|
|
