rmessing171
asked on
Citrix Streaming Publishing: Extra Command Line Parameters - Can not handle filename with spaces.
I am using Citrix XenApp 4.5 and I am streaming application from the server. I am publishing a MS Access database. Therefore, I am pointing my profile to Office.prof.
The Application to Launch is soecified as Microsoft Access 2003.
The Extra Command Line Parameter - points to the UNC path of the database, but the database filename has a space in it:
"\\server1\test\database rules test.mdb" %**
When this profile is streamed, I get an error in MS Access and the filename is truncated on the space - therefore, it shows:
Can not open - "\\server1\test\database.m db"
I have seen writeups about this on the Citrix Forum, however, there are no solutions for Streaming from the Server.
The Application to Launch is soecified as Microsoft Access 2003.
The Extra Command Line Parameter - points to the UNC path of the database, but the database filename has a space in it:
"\\server1\test\database rules test.mdb" %**
When this profile is streamed, I get an error in MS Access and the filename is truncated on the space - therefore, it shows:
Can not open - "\\server1\test\database.m
I have seen writeups about this on the Citrix Forum, however, there are no solutions for Streaming from the Server.
can you shorten the database name and get it to work?
ASKER
I can not try that right now, the client does not want to shorten the name, as well as, they do not want to replace the spaces with underscores.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The client will not change the name of the database. I had seen the citrix article you referenced and the solution does not work for streaming from the server. It only works for Streaming from the Client.
sorry, I meant try using the Extra Command Line Parameter path as 8.3
ASKER
can you take my example of "\\server1\test\database rules test.mdb" and show me how you make it 8.3?
\\server1\test\databa~1.md b
Could you copy the database local to the server and try that path?
If that does not work perhaps you could try having the Extra Command Line Parameter go to a batch file that opens the database.
Could you copy the database local to the server and try that path?
If that does not work perhaps you could try having the Extra Command Line Parameter go to a batch file that opens the database.
ASKER
dborger,
I think you are getting close for me. I have not tried the 8.3 naming convention, but will try it when I get a moment.
Per the batch file called in the Extra Command Line Parameter, how would I specifiy to call the batch file in the Extra Command line parameter, so:
I am telling it to execute msaccess.exe as the target, but how would the EXtra Command Line Parameter look to call the batch, I just can not say:
Target: C:\msaccess.exe
Extra Command Line: M:\database.bat
Do I need a pipe (|) to the information?
Please let me know when you get a quick moment.
Thank you for your awesome assistance!
I think you are getting close for me. I have not tried the 8.3 naming convention, but will try it when I get a moment.
Per the batch file called in the Extra Command Line Parameter, how would I specifiy to call the batch file in the Extra Command line parameter, so:
I am telling it to execute msaccess.exe as the target, but how would the EXtra Command Line Parameter look to call the batch, I just can not say:
Target: C:\msaccess.exe
Extra Command Line: M:\database.bat
Do I need a pipe (|) to the information?
Please let me know when you get a quick moment.
Thank you for your awesome assistance!
the batch file would be something like this.
start C:\folder\database rules test.mdb
start C:\folder\database rules test.mdb
ASKER
Thanks! So just to recap, if I was to run it from a command line or run without the batch file:
c:\msaccess.exe start c:\folder\database rules test.mdb
c:\msaccess.exe start c:\folder\database rules test.mdb
ASKER
The 8.3 naming convention worked. I tried using a BAT file in the Extra Command Line Paramters and it did not work.