Digital Workshop

Can anyone shed some light on this problem for me?

I have made a publication which writes info to a couple of databases.
Another page in this publication queries the databases.

All this is fine and works well in preview, but as soon as I publish it I seem to lose all info held in databases including my prebuilt tables. The file size of the db after this happens is 0kb.

Can anyone offer any help?

Edit: After running my published exe. the databases are also unable to open with Access. I get an error message telling me its not a valid file type.

I am running Access 2000 and Opus Pro 5.5 all on Windows 2000

I am publishing on to a network. I dont know if this has something to do with it but the files are on the network when previewing and this works great!

After thinking about this again, I tried republishing my presentation to a different path then cut and pasting into its final destination.

This worked and allowed me to use my db's as intended.

Opus does ask if you would like to overwrite when publishing to an existing directory but it seems that it also overwrites your database if its in that said directory!

I did have a few other files in this directory which relate to the publication. None of these files were harmed when publishing so why does the database get wiped?

This is a pain, especially if you have a lot of work in the database!

never mind, alls well now

Jim

Hello all,


I have simular problems after publishing my publication. I use opus 5.5XE.
In preview mode i have no problems getting all my data from a Mysql database. But after publishing some parts return undefined.

It's pretty though trying to understand the problem, because it only happens after publishing. [edit: not true...]

I get data from the mysql database using a ODBC- connection and execute sql like this: records = db.ExecuteSQL(sql);

What can be the problem. This is pretty anoying.

My problem seems to be the next line of code:



In preview mode it returns the right number of rows. After publishing, it stops the code. No crash, but it stops the execution of the script.

[edit: ]
The reason it did work when previewing, was the reason the preview used another database (other .ini file). Now using the same database, the problem also happens when using the preview.

Will look further for clues.......