Re: AW: [development-axapta] Report Orientation and Dot-matrix printer

2004-06-28 Thread kam tt
Thanks Steeve Gilbert and Herbert.
But the problem is, in Axapta, if I force to
Protraits, the length is only 8.27 inches(std A4
protraits). So if my report is longer then that,
Axapta automatically set it for me as Landscape.

So once it is Landscape format, I cannot change back
to Protrait at windows enviroment.

Another words, I would like to have a report which
width is longer then 8.27 inches and yet would like to
set up as a Protrait at Axapta.

Sound wired? Please advice me. :(





--- Mister L [EMAIL PROTECTED] wrote:
 There's a nice way to create your own paper-size for
 every printer. It's a
 windows-tool.
 
 Open the window for your printers and fax, go to
 File, and then choose
 Servereigenschaften (I think it is called Server
 options or properties
 in english).
 
 
 | -Ursprüngliche Nachricht-
 | Von: 
 [mailto:[EMAIL PROTECTED] 
 | Gesendet: Montag, 28. Juni 2004 13:56
 | An: [EMAIL PROTECTED]
 | Betreff: RE : [development-axapta] Report
 Orientation and 
 | Dot-matrix printer
 | 
 | You can force orientation by setting the
 ReportDesign 
 | property Orientation.  But for paper format I
 don't know.
 | 
 | Steeve... 
 | 
 | 
 | -Message d'origine-
 | De : kamtt [mailto:[EMAIL PROTECTED]
 | Envoyé : 25 juin 2004 11:07
 | À : [EMAIL PROTECTED]
 | Objet : [development-axapta] Report Orientation
 and Dot-matrix printer
 | 
 | Dear everyone,
 | I would like to know that is there a way to setup
 the width 
 | of a report page and force its orientation to
 Protrait? In 
 | another word, is there a customer page format
 instead of A4 
 | size protrait and Landscape?
 | 
 | The reason is I need to print in Dot-matrix
 printer and if I 
 | change it to Landscape(Or if it is Auto and larger
 then 
 | normal A4 width, Axapta will automatically change
 it to 
 | Landscapre orientation ), it print out in rotated
 90 degree 
 | format(tilted 90 degree way) :(
 | 
 | My printer is OKI ML591 and the report requried
 design is in 
 | A4 Landscape width with feeder format ones.
 | 
 | Please advice me.
 | 
 | Thanks in advance.
 | kamtt
 |  
 | 
 | 
 | 
 | 
 | 
 |  
 | Yahoo! Groups Links
 | 
 | 
 | 
 |  
 | 
 | 
 | 
 | 
 |  Yahoo! Groups Sponsor 
 | ~-- Make a clean sweep of
 pop-up ads. 
 | Yahoo! Companion Toolbar.
 | Now with Pop-Up Blocker. Get it for free!
 |

http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM
 |

--
 | --~- 
 | 
 |  
 | Yahoo! Groups Links
 | 
 | 
 | 
 |  
 | 
 
 
 





__
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



 Yahoo! Groups Sponsor ~-- 
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/saFolB/TM
~- 

 
Yahoo! Groups Links

* To visit your group on the web, go to:
 http://groups.yahoo.com/group/development-axapta/

* 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/
 




RE: [development-axapta] Customised Filtering

2004-04-30 Thread kam tt




Dear Amit and Harry,
Thanks for your prompt answer and sorry for my late
reply as I am a slow learner. 
I've successful it by using sysTableLookup. Below is
my code. 
Thanks again Amit and Harry.
Bye
kamtt 

public void lookup()
{
 Query query = new Query();
 QueryBuildDataSource queryBuildDataSource;
 QueryBuildRange queryBuildRange;
 SysTableLookup sysTableLookup =
SysTableLookup::newParameters(tableNum(custTable),this);
 ;

 sysTableLookup.addLookupfield(fieldNum(custTable,
accountNum));
 sysTableLookup.addLookupfield(fieldNum(custTable,
Name));
 queryBuildDataSource
=query.addDataSource(tableNum(custTable));
 queryBuildRange =
queryBuildDataSource.addRange(fieldNum(custTable,
accountNum));
 queryBuildRange.value(CallerTable_CallerId.text());

 sysTableLookup.parmQuery(query);
 sysTableLookup.performFormLookup();
}


--- Deshpande, Harry [EMAIL PROTECTED]
wrote:
 hi Amit!
 
 Hmmm, I guess adding a new datasource is better than
 adding a new field or
 creating a new look up form, but personally speaking
 I avoid adding a new
 datasource unless its absolutely required. Just my
 way of thinking. no real
 rational behind this.
 
 regards
 
 harry
 
 -Original Message-
 From: Amit Jain [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, April 28, 2004 6:09 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Customised
 Filtering
 
 
 Hi Harry
 
 First thing i m not suggesting that Kamtt should
 create another field for
 itemgroup, but from the statement of Kamtt it looks
 like that they are
 already using ItemGroup field in SalesLine table. If
 creation of new field
 is a problem then might be he can create a new
 datasource for ItemGroup and
 then use sysTableLookTable class. but i won't
 suggest creation of new forms
 only for look until and unless it cannot be done
 another way. This is what
 my personal experience says. 
 
 What ur opinion.
 
 
 
 Regards
 
 Amit
 
 
 
 Deshpande, Harry [EMAIL PROTECTED]
 wrote:
 
 hi Amit!
 
 Interesting!
 
 The problem with what you are proposing is ...
 
 Either I have to create a field to hold the value of
 'ItemGroupId' on
 salesLine. This field does not serve any purpose
 after a line has been
 created and violates the 'Normalization' rule for
 the data. It also takes up
 unnecessary disk space.
 
 One can also create just an extended data type field
 on the saleTable form
 (in the sales line grid). However, this means..if i
 specify an item group
 and go to second line to specify a different item
 group the first item group
 changes. This will create confusion for the viewer.
 
 This is why I recommended a different lookup form on
 the ItemId with two
 tabs like the 'location' look up form.
 
 Do let me know if you find some problem with the
 above thinking.
 
 regards
 
 harry
 
 -Original Message-
 From: Amit Jain [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, April 28, 2004 4:50 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [development-axapta] Customised
 Filtering
 
 
 Hi
 
 For this u must have created a data field for
 itemgroup in the salesline
 form. you can anytime override the lookup method of
 the itemid field in
 SalesLine datasource to control the way look up
 behaves. All you have to do
 is use sysTableLookup Class. Refer Axapta's help for
 this. If you still face
 problem then let me know.
 
 
 Regards
 
 Amit
 
 Deshpande, Harry [EMAIL PROTECTED]
 wrote:
 
 hi
 
 On second thoughts...
 
 It will be better if you could change your look up
 form on the item id to
 the format of the look up form on the field
 warehouse (on salesline). So the
 new lookup with have two tabs. On first tab show
 itemgroup and on second tab
 show related items. this will make things easier.
 
 regards
 
 harry
 
 
 -Original Message-
 From: kamtt [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, April 27, 2004 7:18 PM
 To: [EMAIL PROTECTED]
 Subject: [development-axapta] Customised Filtering
 
 
 Hello,
 I am new for Axapta and I have encounter below
 problem.
 In Sales Line of Sales Order, I would like to select
 an ItemGroup 
 first and then it will automatically filter and
 shows for Item 
 Numbers which are only related to selected
 ItemGroup.
 
 I don't want to jump to Item Number and filter using
 standard. In 
 this way, user need to select ItemGroup first and
 and it will show 
 filtered Item Numbers when he dirll down on Item
 Number field. 
 
 Please advice me how to solve the problem.
 
 Thanks in advance,
 kamtt
 
 
 
 
 
 _ 
 
 Do you Yahoo!?
 Win

http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/hotjobs_mail_signature_

footer_textlink/evt=23983/*http://hotjobs.sweepstakes.yahoo.com/careermakeov
 er a $20,000 Career Makeover at Yahoo! HotJobs 
 
 
 
 _ 
 
 Do you Yahoo!?
 Win

http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/hotjobs_mail_signature_

footer_textlink/evt=23983/*http://hotjobs.sweepstakes.yahoo.com/careermakeov
 er a $20,000 Career Makeover at Yahoo! HotJobs 
 
 _ 
 
 Yahoo! Groups Links
 
 
 * To visit your group