The answer to my question is this. A new class was created in a lower layer by the name of X. What happens when this class is created it now becomes an object and not a variable. Since X ia an object now it cannot be used as a variable. Then you will get an syntax error anywhere it is declared as Int h,x,y;
Myrl Thanks all for responding. P.S. Looks to me that the axapta standard when using naming conventions is to use a 3 letter sufix to signify what module you are working with. ex. smm, BAS, BM, CAC, HRM etc.. For us when different consultants work on our system and create new objects I ask them to always use the first 3 letters of the company they work for. Just for accountability. -----Original Message----- From: Cliff Dols [mailto:[EMAIL PROTECTED] Sent: Friday, February 18, 2005 12:47 AM To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] Re: High Importance!!!! Syntax error after a Int declaration. Myrl, I think it has to with the order in which you call the integers. You first have to call the integer that is declared first and so on... Maybe you have thought of this already, but it could solve your problem Grtz, Cliff Sharing the knowledge on Axapta. Yahoo! Groups Links ------------------------ Yahoo! Groups Sponsor --------------------~--> What would our lives be like without music, dance, and theater? Donate or volunteer in the arts today at Network for Good! http://us.click.yahoo.com/Tcy2bD/SOnJAA/cosFAA/kGEolB/TM --------------------------------------------------------------------~-> Sharing the knowledge on Axapta. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Axapta-Knowledge-Village/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
