Error In Equation Illegal Syntax Great Plains
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
Topic Search Topic OptionsPost ReplyCreate New Topic Printable Version Translate Topic LA_CAL Members Profile Find Members Posts MicrosoftDynamicsForums.com Member Joined: June152006 Location: United States Status: Offline Points: 124 Post Options Post Reply QuoteLA_CAL Report Post Thanks(0) QuoteReply Topic: Error in EquationPosted: December192006 at 10:27am I am customizing a report and now when I run the report it gives me this error: Error in equation '***ILLEGAL SYNTAX *** [ Not found ] How would I know where is the problem? Sponsored https://groups.google.com/d/topic/microsoft.public.greatplains/1uCnbQuKLqM Links LA_CAL Members Profile Find Members Posts MicrosoftDynamicsForums.com Member Joined: June152006 Location: United States Status: Offline Points: 124 Post Options Post Reply QuoteLA_CAL Report Post Thanks(0) QuoteReply Posted: December192006 at 11:34am In other words, is there anything called running a GP report in debug mode, so that I could find out what is causing the above error? Joseph A http://www.microsoftdynamicsforums.com/forums/forum_posts.asp?TID=916 Nader Members Profile Find Members Posts Visit Members Homepage MicrosoftDynamicsForums.com Member Joined: September142006 Location: Lebanon Status: Offline Points: 360 Post Options Post Reply QuoteJoseph A Nader Report Post Thanks(0) QuoteReply Posted: December192006 at 11:27pm Normally, you receive this error when you have created a calculated field using an incorrect syntax. For example, choosing an integer type for a calculated field that gives a string will give the syntax error. Check any new calculated fields and test. Take Care Joseph Abou Nader, PMPMCT,MCTS,MCBMSS,MCSA LA_CAL Members Profile Find Members Posts MicrosoftDynamicsForums.com Member Joined: June152006 Location: United States Status: Offline Points: 124 Post Options Post Reply QuoteLA_CAL Report Post Thanks(0) QuoteReply Posted: December202006 at 7:42am I have checked each and every report calculated field but couldn't find anything wrong. After spending five hours in debugging this error, I am starting again, I think that might take less time. Joseph A Nader Members Profile Find Members Posts Visit Members Homepage MicrosoftDynamicsForums.com Member Joined: September142006 Location: Lebanon Status: Offline Points: 360 Post Options Post Reply QuoteJoseph A Nader Rep
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be http://www.tek-tips.com/viewthread.cfm?qid=1136567 Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums http://dynamicsgpblogster.blogspot.com/2009/06/fixing-microsoft-dynamics-gp-and.html Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: error in jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Microsoft: Dynamics GP (Great Plains) Forum at Tek-Tips HomeForumsEnterprise ApplicationsERP and CRM Solution VendorsMicrosoft: Dynamics GP (Great Plains) Forum Error in Equation ILLEGAL SYNTAX when error in equation printing checks thread632-1136567 Forum Search FAQs Links MVPs Error in Equation ILLEGAL SYNTAX when printing checks Error in Equation ILLEGAL SYNTAX when printing checks barbola (TechnicalUser) (OP) 13 Oct 05 12:07 I made a change to the check remittance reports to add a sort order equal to document number. One user (one client workstation) was trying to print cheques, and the remittance was coming up with headings that say "not found".She had imported the modified report properly, and I noticed the Restrictions all said "not found", so on her machine, I re-entered the restrictions.Two of the reports work (Cheque Remittance and Cheque Remittance w/o headers) but the Check with Stub on Bottom gives the error.I even completely took out the restrictions, added them back one by one, and get the error every time.I checked this users security and it's fine...I even used the 'sa' login.I imported the report as a customization package first and then drectly from my reports.dic.Any ideas? Thanks!Barb E. RE: Error in Equation ILLEGAL SYNTAX when printing checks barbola
you probably read David Musgrave's series on Microsoft Dynamics GP and Illegal Characters and have come to realize that the single quote character is perhaps one of the biggest culprits in the errors you are receiving when running reports such as your age trial balances in both receivables and payables. It's enough for the single quote character to be in your customer ID, vendor ID, or even document numbers to cause some error while running a report or inquiring a transaction.The following is an actual case reported by a user on the Dynamics GP newsgroup when running the Payables Historical Aged Trial Balance report:The stored procedure pmHistoricalAgedTrialBalance returned the followingresult: DMBS: -127, Microsoft Dynamics GP: 0.After some research the user realized they had a few document numbers that contained the illegal single quote character, for example INV'23002. Note that this case is specific to the document number.So, what to do if you are a victim of the single quotes?1) You will need to first identify the tables possibly affected. In particular, you will need to search all tables in the database that may contain the column storing the data -- in the case of the example, DOCNUMBR. For this you can use a script I published before here. You may also use the script provided by David Musgrave on Part 2 of his series, which would allow you to search through all your company databases if experiencing the issue in more than one company.2) You will then need to identify the specific records affected by a single quote. Once the tables have been identified, you can do the following:SELECT * FROM PM00400 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM10201 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM10300 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM10400 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM20000 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM30200 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM50100 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM PM80200 WHERE DOCNUMBR LIKE '%''%'SELECT * FROM GL20000 WHERE ORDOCN