Digital Workshop

Hi,

I've noticed a difference in how Windows handles FILEDSN under Windows XP and Windows 7.

Windows 7 looks like this:
FILEDSN=C:\Users\User Name\Documents\MY_Database.dsn;

Windows XP looks like this:
FILEDSN=MY_Database.dsn;


Normally under Windows XP I would create the DSN, and have it setup through the usual steps. I would then create a variable called DB_FileDNS. This variable would contain FILEDSN=MY_Database.dsn (This was so I could change the database DSN at a later stage without the need of edition 80 scripting pages.)

So then in all scripting pages that needs access to the database for SQL statements I would have the following line of code at the top of the script.




The problem is with Windows 7, if I set var DB_FileDNS = FILEDSN=C:\Users\User Name\Documents\MY_Database.dsn
It doesn't work.

If I set DB_FileDNS = FILEDSN=MY_Database.dsn
I get a problem of two database DSN listed in the database tab, this one not being linked to an actual database, so what is Opus doing with it?

I never had this issue with Windows XP, anyone got any suggestions?

I'm a little lost, but here it goes.

The creation of a ODBC FILEDNS under XP or W7 appears the same (excludes 64bit). The process creates a *.dsn file somewhere on your hard drive of your choosing.

The *.dsn file contains the ODBC information about where the DB is located and the driver used for connection.

In Opus, you specify where the *.dsn file is using new Database and assign this to a variable. This creates an entry in the Database tab.

When published the database is copied to the publication folder and the *.dsn is not required for distribution. You can specify a different location for the DB when published and this is advisable under Vista / W7.

Mack

Thanks for reply.

I think the issue was arising as I was developing on both Windows XP and Windows 7 with all development files on an external hard drive.

When I moved between them I had to change my var DSN settings. I have it all working now I think.

As long as any absolute path is the same, then it should work. The alternative is to use something like the SYSTEM_PUBLICATION_DIR and keep it all relative.

Mack

Oh yeah when published I always use SYSTEM_PUBLICATION_DIR, just in the editor it was causing the issue the different way Windows 7 and XP handle DSN.

Has to do with the new My Documents system in Windows 7, which still confuses me, I'm not a fan of the new Libraries folder.