I'm trying to connect to a database with a filename containing Chinese
characters.
The full path to my file is: C:\Users\汉密斯\AppData\Local\Rising
Software\data5cloud\rising5.fdb
I'm not able to connect to this filename - I'm always told that the path
name is wrong. I've tried using the full name as above, and also
converting it to Windows short filename syntax which is
C:\Users\F1DC~1\AppData\Local\RISING~1\DATA5C~1\rising5.fdb, but neither
work. It doesn't matter if I use the embedded server (Windows) or network.
If I use the proper name:
C:\>dir "C:\Users\汉密斯\AppData\Local\Rising
Software\data5cloud\rising5.fdb"
Volume in drive C has no label.
Volume Serial Number is 5837-4B6E
Directory of C:\Users\汉密斯\AppData\Local\Rising Software\data5cloud
10/03/2017 10:08 AM 58,019,840 rising5.fdb
1 File(s) 58,019,840 bytes
0 Dir(s) 46,259,064,832 bytes free
C:\>isql "C:\Users\汉密斯\AppData\Local\Rising
Software\data5cloud\rising5.fdb"
Statement failed, SQLSTATE = 08001
I/O error during "CreateFile (open)" operation for file
"C:\USERS\???\APPDATA\LOCAL\RISING SOFTWARE\DATA5CLOUD\RISING5.FDB"
-Error while trying to open file
-The filename, directory name, or volume label syntax is incorrect.
Use CONNECT or CREATE DATABASE to specify a database
If I use the short name:
C:\>dir C:\Users\F1DC~1\AppData\Local\RISING~1\DATA5C~1\rising5.fdb
Volume in drive C has no label.
Volume Serial Number is 5837-4B6E
Directory of C:\Users\F1DC~1\AppData\Local\RISING~1\DATA5C~1
10/03/2017 10:08 AM 58,019,840 rising5.fdb
1 File(s) 58,019,840 bytes
0 Dir(s) 46,259,068,928 bytes free
C:\>isql C:\Users\F1DC~1\AppData\Local\RISING~1\DATA5C~1\rising5.fdb
Statement failed, SQLSTATE = 08001
I/O error during "CreateFile (open)" operation for file
"C:\Users\F1DC~1\AppData\Local\RISING~1\DATA5C~1\rising5.fdb"
-Error while trying to open file
-The filename, directory name, or volume label syntax is incorrect.
Use CONNECT or CREATE DATABASE to specify a database
Ultimately I'm trying to connect from a Qt application, but I've tried
the above with isql just to rule out errors with the db driver.
Any ideas?
Thanks
Hamish
