Hi Harry,
from my experience i feel there is always an
advantage of naming with identifier as a prefix. i.e
if your client's name is ABCDE then you could pick the
first 3 digits and then write "ABC_TableName1". some
of the advantages are:
1. if you want to include the new tables created in
the defination group (to import/export the data) then
its easier to understand which tables to pick.
2. if you press F2 and want to pick up the new table
created its easier to identify the tables as they all
are listed one after the other. similarly when
selecting EDT and enums from the short cut.
There are so many other instances where adding
the identification as a prefix would help a lot. It
might be possible to even identifing by adding suffix
but prefix makes things easier, atleast for me.
By adding the identification as a suffix we can
maintain the other naming convention rule where in we
add the prefix to identify the business area. But we
could add the identifier then underscore and then the
busniess area of the element.
cheers,
Girish
--- Harry Deshpande <[EMAIL PROTECTED]> wrote:
> Hi Girish
>
>
>
> "It is
> always better we add some prefix so that it will
> never
> affect the standard functionality..."
>
>
>
> Or may be use a suffix *s*
>
>
>
> Regards
>
>
>
> harsh
>
>
>
> _____
>
> From: Girish B [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 17 February 2005 11:45 p.m.
> To: Axapta-Knowledge-Village@yahoogroups.com
> Subject: RE: [Axapta-Knowledge-Village] High
> Importance!!!! Syntax error
> after a Int declaration.
>
>
>
> Guys,
> This problem is one of the instance where the
> naming convention what we follow affect the standard
> functionality aswell.
> When ever we create/modify in standard axapta we
> should be carefull of what name we are giving. It is
> always better we add some prefix so that it will
> never
> affect the standard functionality...
> In this example we all know that at many places
> x,y,z
> and a,b,c would be used so we should avoid using
> these
> for naming the new EDT. If you do want to display
> x,y,z etc.. then you could label the elements with
> these but the element name should be given a prefix.
> It is very important for new axapta developers
> to
> start using some standard naming conventions because
> you will get used to this standard practice, else to
> change in the later stage becomes a bit difficult,
> but
> still posssible.
>
> !!!!Enjoy coding!!!
>
> cheers,
> Girish
>
>
> --- Padmaja Iyingar <[EMAIL PROTECTED]> wrote:
>
> > Hi Preston,
> >
> > Its perfect. Your assumption is right. I tried to
> > change to
> >
> > real _quantity, _price from real quantity,
> price..
> >
> > ha ha ha ha..It wroks now.
> >
> > Thanks Preston for the tip.
> >
> > regards,
> > Subbu
> >
> > "Preston A. Larimer" <[EMAIL PROTECTED]> wrote:
> > v\:* {behavior:url(#default#VML);}o\:*
> > {behavior:url(#default#VML);}w\:*
> > {behavior:url(#default#VML);}.shape
> >
>
{behavior:url(#default#VML);}st1\:*{behavior:url(#default#ieooui)
> > }
> > More than likely some one has added a new EDT
> named
> > either x, y, or z. When you have a declaration
> like
> > this
> >
> >
> >
> > Int x, y, z;
> >
> >
> >
> > Then later add a new EDT of the same name as x, y,
> > or z you will get compile errors on existing
> classes
> > that have the above declaration, the fix is to
> find
> > your new EDT, and rename it, or modify the class
> so
> > the declaration is on multiple lines such as
> >
> > Int x;
> >
> > Int y;
> >
> > Int z;
> >
> >
> >
> > You can file this with the bug where you have to
> use
> > a semi-colon (;) on a blank line to signify that
> > declarations have ended and code starts when your
> > first line of code starts with a variable having
> the
> > same name as an Axapta EDT, Table or Class.
> >
> >
> >
> > -Preston
> >
> >
> >
> > ---------------------------------
> >
> >
> > From: Subrahmanyam Mamidi
> > [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, February 16, 2005 8:03 PM
> > To: Axapta-Knowledge-Village@yahoogroups.com
> > Subject: Re: [Axapta-Knowledge-Village] High
> > Importance!!!! Syntax error after a Int
> declaration.
> >
> >
> >
> >
> > Just checked it now. its happening in 3 tier. not
> in
> > 2 tier. I am using AX3 , SP3 full patches
> > applied....
> >
> >
> >
> >
> > Is anyone having the same problem??
> >
> > thanks,
> >
> > Subbu
> >
> >
> >
> > Subrahmanyam Mamidi <[EMAIL PROTECTED]> wrote:
> >
> >
> > Today it happend to me AX3.0 SP3.0........
> >
> >
> >
> >
> >
> > real x,y,z; won't compile where as
> >
> >
> >
> >
> >
> > real x;
> >
> >
> > real y;
> >
> >
> >
> >
> >
> > real z;
> >
> >
> >
> >
> >
> > will compile..............
> >
> >
> >
> >
> >
> > Will look into other rnvironments though...
> >
> >
> >
>
=== message truncated ===
___________________________________________________________
ALL-NEW Yahoo! Messenger - all new features - even more fun!
http://uk.messenger.yahoo.com
------------------------ Yahoo! Groups Sponsor --------------------~-->
Has someone you know been affected by illness or disease?
Network for Good is THE place to support health awareness efforts!
http://us.click.yahoo.com/Rcy2bD/UOnJAA/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/
