Axapta is running on the terminal server, not the client pc in this case. Thats a problem. The only way to get around this that I can see is one of two options: 1. Toss the terminal server. Run Axapta on the POS machines themselves. 2. Write a small app that performs the functions you want, and then integrate it using the business connector with axapta. This small app would thenhave to run on the POS machine, but could run as a service that the user doesn't see or interact with. Of course, doing this removes the advantage of not having to deploy to each client pc, but does allieviate the network bandwidth issues. Another downside is that you would probably need double the axapta liscences as each business connector connection would count as well as the user logged in via TS.
--- On Fri, 6/20/08, tavocol2002 <[EMAIL PROTECTED]> wrote: From: tavocol2002 <[EMAIL PROTECTED]> Subject: [development-axapta] OPEN CASH MACHINE HELP To: [email protected] Date: Friday, June 20, 2008, 3:16 PM Hi Folks. I have an EPSON TM-U220PD and my customer wants to implement a P.O.S. I have this case scenario: An AX Server - Terminal Server - Final user logging trough Terminal Server to work with AX - Cash Machine on Local PC. The question is How can i open the Cash Machine that is connected to the Final User PC if I'm running AX trough Terminal Server on that PC??? I don't know how to handle this because if i compile a DLL i don't know how to handle the local devices instead the server devices and terminal devices :S Anybody can help me with this trouble, i accept any kind of help.... links, references, code, anything. I have to remark that i'm not a .NET expert at all, so, be kind :D Gustavo Camargo Téllez MDO Consultores S.A. Microsoft Gold Certified Partner Bogota - Colombia (South America) [Non-text portions of this message have been removed]
