RE: [development-axapta] Re: Top margin changes by itself
Thanks Karsten, I would say its somewhat of a bug because yes I agree I could program the report based on knowing the printer but these days this is often not the case. Customers see printers as plug and play etc and to ask them to say which printer in a multi site environment is for sure going to be thrown back from the customer My frustration is that export and import steps change the AOT property so now you have to be sure any person doing such is having the right printer (and the right default windows printer as far as I can tell). In most reports that are just listings its not a big issue but things like cheque printing where exact printing is required then its a real pain to have to make sure the programmer does not have any printer installed on their PC before they can edit and save the object! Going forward I guess the advice is for exact printing report the dev needs to have the driver installed and set as teh default printer when doing anything with such objects... Thanks James _ From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of Karsten Krabbes Sent: 18 March 2009 16:46 To: development-axapta@yahoogroups.com Subject: [development-axapta] Re: Top margin changes by itself Hi James, this is not a bug, its a feature :-) You face this problem everywhere in the windows world as the margins always depends on the actual printer driver and also on the hardware !. That means you should alway develop a report with the printer driver you want to use it with. If the positions on the paper are not that important and you use different printers in your company you could just set the property 'fit to page' to yes. Another approach to solve this is to read the actual top margin from the driver and calculate all the positions in the report in run time ... br Karsten --- In development- mailto:development-axapta%40yahoogroups.com axa...@yahoogroups.com, James Flavell djf1...@... wrote: Hi everyone Just spent most of the day with a strange problem regarding the top margin property on a design section of a report. The situation is: Client PC has no windows printers installed Using this client set the top margin to 4.2mm in an AX4.0 SP2 report Install a pritner on this client PC Log back into AX and when look at the property it is now 6.27mm and cannot be changed to be less (this change happens without any edit of the report object!!!) I am guessing that somehow AX tries to be smart and says the minimum top margin is 6.27mm Is this some kind of hard coded size? Or does AX AOT reports somehow check the default windows printer?!!! Look forward to hearing from you Thanks James [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
RE: [development-axapta] Re: AOS doesn't Start due to SQL login Error
Dear Abhay, there are two possibilities for this Error as i think: 1. Goto AOS, and check under Server Configuration Utility that is there DataBase name is correctly assign. 2. Check the User Name and its Passwords. it should be setup properly. hope you can find solution after these steps. regards. KHALIL UR REHMAN To: development-axapta@yahoogroups.com From: kuet...@live.com Date: Tue, 17 Mar 2009 13:30:17 + Subject: [development-axapta] Re: AOS doesn't Start due to SQL login Error You can't use a local account when Sql is on a different server. See here for more on the topic: http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.axapta.programmingtid=a1ce9574-d58a-4e67-9e16-6c66df5ea081cat=lang=encr=USsloc=p=1 --- In development-axapta@yahoogroups.com, Abhay ab...@... wrote: When i try start AOS from services it can't start. I try it for Local system account . In the Event viewer i got the followng messages... Plz any one can tell the solution for thisSQL diagnostics: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.. Connect information was: Userid = [], Database = [OBSSMD_US], Server = [OBS-DYNAMICS-DB], DSN = [], Other = [] Fatal SQL condition during login. Error message: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.Regards Abhay [Non-text portions of this message have been removed] _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us [Non-text portions of this message have been removed]
Re: [development-axapta] Re: AOS doesn't Start due to SQL login Error
I think you are using Ax-3.0 version but I want for Ax4.0 versionRegards Abhay -Original Message- From: Khalil Rehman khalilrehm...@hotmail.com Sent 3/17/2009 7:34:42 PM To: development-axapta@yahoogroups.com Subject: RE: [development-axapta] Re: AOS doesn't Start due to SQL login Error Dear Abhay, there are two possibilities for this Error as i think: 1. Goto AOS, and check under Server Configuration Utility that is there DataBase name is correctly assign. 2. Check the User Name and its Passwords. it should be setup properly. hope you can find solution after these steps. regards. KHALIL UR REHMAN To: development-axapta@yahoogroups.com From: kuet...@live.com Date: Tue, 17 Mar 2009 13:30:17 + Subject: [development-axapta] Re: AOS doesn't Start due to SQL login Error You can't use a local account when Sql is on a different server. See here for more on the topic:http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.axapta.programmingtid=a1ce9574-d58a-4e67-9e16-6c66df5ea081cat=lang=encr=USsloc=p=1 --- In development-axapta@yahoogroups.com, Abhay ab...@... wrote: When i try start AOS from services it can't start. I try it for Local system account . In the Event viewer i got the followng messages... Plz any one can tell the solution for thisSQL diagnostics: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.. Connect information was: Userid = [], Database = [OBSSMD_US], Server = [OBS-DYNAMICS-DB], DSN = [], Other = [] Fatal SQL condition during login. Error message: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.Regards Abhay [Non-text portions of this message have been removed] __ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
RE: [development-axapta] Re: Top margin changes by itself
Hi James If the thing that's causing you the problem is that the import process changes the margin to match the physical limitations of the default printer of the user that did the XPO import, what would happen if you imported the object using an account that has no default printer (or perhaps no printer defined at all). It would probably mean having a domain account used only for doing XPO imports but if that solves your problem it would be a small price to pay. Malcolm From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of James Flavell Sent: 19 March 2009 06:00 To: development-axapta@yahoogroups.com Subject: RE: [development-axapta] Re: Top margin changes by itself Thanks Karsten, I would say its somewhat of a bug because yes I agree I could program the report based on knowing the printer but these days this is often not the case. Customers see printers as plug and play etc and to ask them to say which printer in a multi site environment is for sure going to be thrown back from the customer My frustration is that export and import steps change the AOT property so now you have to be sure any person doing such is having the right printer (and the right default windows printer as far as I can tell). In most reports that are just listings its not a big issue but things like cheque printing where exact printing is required then its a real pain to have to make sure the programmer does not have any printer installed on their PC before they can edit and save the object! Going forward I guess the advice is for exact printing report the dev needs to have the driver installed and set as teh default printer when doing anything with such objects... Thanks James _ From: development-axapta@yahoogroups.commailto:development-axapta%40yahoogroups.com [mailto:development-axapta@yahoogroups.commailto:development-axapta%40yahoogroups.com] On Behalf Of Karsten Krabbes Sent: 18 March 2009 16:46 To: development-axapta@yahoogroups.commailto:development-axapta%40yahoogroups.com Subject: [development-axapta] Re: Top margin changes by itself Hi James, this is not a bug, its a feature :-) You face this problem everywhere in the windows world as the margins always depends on the actual printer driver and also on the hardware !. That means you should alway develop a report with the printer driver you want to use it with. If the positions on the paper are not that important and you use different printers in your company you could just set the property 'fit to page' to yes. Another approach to solve this is to read the actual top margin from the driver and calculate all the positions in the report in run time ... br Karsten --- In development- mailto:development-axapta%40yahoogroups.com axa...@yahoogroups.commailto:axapta%40yahoogroups.com, James Flavell djf1...@... wrote: Hi everyone Just spent most of the day with a strange problem regarding the top margin property on a design section of a report. The situation is: Client PC has no windows printers installed Using this client set the top margin to 4.2mm in an AX4.0 SP2 report Install a pritner on this client PC Log back into AX and when look at the property it is now 6.27mm and cannot be changed to be less (this change happens without any edit of the report object!!!) I am guessing that somehow AX tries to be smart and says the minimum top margin is 6.27mm Is this some kind of hard coded size? Or does AX AOT reports somehow check the default windows printer?!!! Look forward to hearing from you Thanks James [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
