Thanks Jonathan, Thats not the problem. Probably the python product converts the path separators if necessary. The Data Adapter has always worked, using paths like c:/localhost:/one/two/data.gdb - it was just the introduction of a connection_string name with SPACES in the data path, eg c:/localhost/ /program^ files/two/data.gdb^userid^password that's causing "invalid connection string" errors. My guess is that the DA is grabbing string parts (path,userid,password) using spaces as delimiters. David ----- Original Message ----- From: "Jonathan Hobbs" <toolkit@magma.ca> To: "David Hassalevris" <bluepaul@earthlink.net>; <zope@zope.org> Sent: Friday, August 06, 2004 4:02 AM Subject: Re: [Zope] Data Adapter connection string and Win32
----- Original Message ----- From: David Hassalevris <snip> I have a client that have their sql (interbase) database in a Windows XP directory: c:\Program Files\Somedirectory\data.gbd.
The problem is that the space betwee Program and Files is causing: Invalid connection string: localhost:c:/Program Files/Eden.gdb sysdba masterkey So I tried quoting as 'localhost:c:/Program Files/SomeDirectory/data.gdb' userid password To separate the path from the userID and password. No luck. </snip>
If you are running under a Windows OS shouldn't the directory separators
be
"\" not the linux variety "/"?
Jonathan