[archive] Spaces in file-paths (call dll)

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

You can set in your configuration file or source program the following:

FILENAME_SPACES = 1

or

set environment 'FILENAME_SPACES' to '1'

Good Luck...


CB52 from the Pampas

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

You can set in your configuration file or source program the following:

FILENAME_SPACES = 1

or

set environment 'FILENAME_SPACES' to '1'

Already tried that one. Doesn't work... :(

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

hi emo, try this
http://www.acucorp.com/support/supported/customer_forum/showpost.php?p=5477&postcount=2

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

Try putting quotes (") around it. I've had to do that for some OS calls...

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

I think I have tried every combination of quotes and hyphens... still no good unfortunately.

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

I have had a similiar issue with this. We were hoping to use the registry setting for the temp data path, but due to the issue with spaces being dropped I was unable to access those locations.

I tried several different variations including moving the value to a working storage variable first. I also tried teh environment setting above with no luck either.

set environment 'FILENAME_SPACES' to '1'
call
"@[display]:'C:\\Program Files\\MountFocus\\Keyboard\\Kbd.exe'"

It just takes out the space in program files which cause a not found. I tried it with and without the @display and with and without the single quotes. I also tried direct calls using single rather than double quotes.

[Migrated content. Thread originally posted on 15 May 2008]

We have a call to a dll like this:


CALL "c:\\program files\\test\\dipdf.dll"
GIVING STATUS-VALUE.

What happen here is that the SPACE in Program Files is dropped, and the resulting call in the Trace-file looks like this:

c:\\programfiles\\test\\dipdf.dll

and it obviously fails.

We have made a workaround like this:

set environment "CODE_PREFIX" to 'c:\\"program files"\\test\\'.

CALL "dipdf.dll"
GIVING STATUS-VALUE.


but I don't really think this is a good solution. I can't imagine that we are the only one who have experienced this problem? Is it possible to solve it in a better way then this? Is it a bug?

Guys, this really sounds like a bug, I suggest you report it, along with a nice smalle example to Tech Support.