Sage 100

On a Citrix Server a client with MAS90 Version 4.4 wants to point GL Exchange Export to a local drive. The Exchange wizard sets the path using UNC path to the client computer and we get and Error ""Invalid Class Strin (err/ret=2/0)."" Anyone have any luck exporting in GL Exchange to the client computer?

You are EXPORTING using Exchange? Why not set up a query in Excel and have client refresh as needed? If you need to put run time variables, this is easy to do also.

I have to admit I used to think all this Excel and Access exporting was silly when Sage provided similar functionality. Until I tried it... I've used MS Access for a few exports and it's got a relatively short learning curve and much easier functionality for exports. Plus in many cases customers like to leverage their existing MS Office skills.

Queries via Excel and Access are better than white bread and Mama's milk. The next thing I am waiting for you to say is that you LOVE Pivot Tables.................. You do have to start worrying about user security once users understand the power of queries. Once they figure out AR Sales History exports,the curious will start working on their PR export skills.................

Anyone who has payroll needs to use ODBC security - people with Excel skills have already figured this out.

@RonGouveiaCPACITP - assuming the Exchange export otherwise works okay, if I recall correctly, Exchange executes the path at the server not the client meaning the UNC to the workstation's local drive should be valid from the server. So if App Server is using LocalSystem account to run or any account where a challenge could appear, the export will fail. You can test by directly logging on to the server using the App Server account. Then in Windows Explorer just try to browse to that UNC path to the wkstn's share. If Windows challenges you with a prompt to provide login - password credentials then that's your problem. Or let's say you're not challenged but can't create files in that share that would cause it too. Before you do any of this, make sure your Exchange export itself work okays when pointing it to a regular path. Hope that helps.

I agree Jeff that the client should be choosing other better and easier means of export. Alnoor, the export works to the citrix box but not to the client workstation. I'm betting the UNC doesn't work from the server. i'll check with client's IT. thanks all.