Digital Workshop

Hi,

I've created a tutorial and I'm writing to an Access database using a file DSN.

All the results are written okay when I run a preview but when I publish tutorial as standalone or web based the data dosn't write.

I created the DSN using the 'Microsoft Access Driver (*.mdb)' driver.

I'm using Opus Pro ver 04.50 on win XP Pro SP2.

This has me driven wrong - please help!!!!

Thanks,
Dermot

I'm really rusty on databases.
When you publish, can you search, but not write to the database?? it sounds like it can't find the database when you publish, but if you can search, then that would blow that idea.

I just found the last database publication I did and checked the DSN. I have the file location as C:\the\path\to \the\database, then I have <SYSTEM_PUBLICATION_DIR> selected for path for file when published. I also have the database as an additional resource and a script alias, but I can't for the life of me remember why I did it or if it's really necessary. ( I only have two brain cells, so I have to choose carefully what I use them for!!) Usually if you publish to the development machine, it will still find the database--it's only if you try to run the publication on another machine and you haven't included the database or referenced it properly that you have problems...but something for you to look at

Dermo,

I had a similar problem a while ago with Opus 5. For some reason the records were not updating the database as they shoul have. After countless efforts I had to go through each action on the database list again, 'Applying' as I went along. This solved it but the cause still remains a mystery.

Let me add a similar problem I experienced. Might help someone.

I had a test pub with a DB. The actions in the Scripts worked in Preview mode, but did not work when I published Standalone.

Steps I took: (hints in other posts... thanks)
1. near the end of Publishing process, click the Radio to "create a Setup program" (or similar wording)
2. in the next stage, "Add files" (or 'Add Directory'). You might 'play' with these choices... makes a difference. I added files... the DB, a DLL, a couple image files, etc. It might better say: "include needed files".
3. then I found it wouldn't work, so before next time republishing... I changed the Script I had in my Pub to the following... Path for the DB, absent the Resource Folder:
SYSTEM PUBLICATION DIRECTORY + "DBfilename.db"
( now this way it would not work in Preview but did in publishing. )

Previously in my Script, I had the folder in the path: SYSTEM PUBLI... + "My Pub Resource folder\\" + "DBfilename.db"

It made a difference of course whether I chose to put the needed files were in the C:\Program Files directory at a level with the executable, or to put them in the appropriately named Resource folder (that the unchanged Script expected).

It's probably one of those things to get in the way once / sometime. I'll stick with using the folder.