Digital Workshop

Hi All,

I have a pub with a page that will have 20 text input boxes ( vaiables / fields ) and i could have up to 100 pages like this this . never wokring with data and OPUS in this way before i need to know the best way to handle the data colected and how to store it if the client clicks " Save ".

I would appreciate any suggestions ,

I am a novice to scripts but an intermediate user of OPUS , i have just never taken on a direction like this before..

Thanks in advance

Al barnes

This is often personal preference, but for something like this, I would use a database, but you could store the data in a text file as well. I've always found the database commands which are built into Opus to be very good. It can also be done in scripting.

Large amounts of organised data, points to a database structure. It's also easy to change the database as you go along.

I've always started with either a spreadsheet or an access database. There is a learning curve to go through, but it's not as difficult as first appears and there are always people ready to help.

I've never used text files for saving large amounts of data, but that is relatively easy to do as well. There are all kinds of commands/scripts to use.
If you search the forum for "database" you will find lots of information which may be useful in helping make a decision.
Sandy

Hi,

I agree with sandyn it is a combination of personal choice, expereince and needs. DBs are slighty harder but if you use scripting you have access to the power of SQL.

Textfiles are to sequenctial for most purposes but with O6 you get the option of reading & writing to INI with is an unusual but useful way of storing certain forms of data.

You need to think carefully about what the data is, for example does it need to be protect - the DP laws in the UK are strick on such things and who needs access to it. For example, several people trying to read / write the same files might cause problems.

Just my 2 cents worth.

Mack

I can see that i am in very sensitive areas here , the data is supposed to be entered and used by 1 person BUT evently the Pub could be used by many ( if i make it that way ) and it will contain sensitive data . MY wife is a Database specialist and i will consult here on making a database .

Now does anyone have an example of a database driven pub that i could look at to get a visual concept of what i am up against LOL.....even a simple example with name -- age---- country would be enough for me to understand its workings...


I appricate your time and i hope that i don't ask any siliy questions..

Al

I think you want to talk to Stephen. He just went through a similar exercise recently, so he will have a lot of useful advice.
Have a look at
viewtopic.php?t=2568&highlight=name+age+database
Sandy

LOL .............that was intense..........

I really got into it though , i will srat playing around this week and let you know how I did . Thanks for the Pointer Sandy

I was going to create a very very simple Database example for you, (name,age,country) but I have somehow created a demon application which crashes the ODBC driver. The example was as basic as you can get, but it is the most troublesome application I have ever created! it causes an ODBC syntax error and Opus to shut down/crash/not respond. I have a few things to try----I'm going to have to eat my words when I said "it is not as difficult as it first appears!!" .
Other database applications I created in the past still work perfectly, so I must have done something stupid.

Having created quite a few DB interfaces using Opus and fixed several more for other people I have to recommend several things:

1. Storyboard your DB application and note on it the neccessary interactions.
2. Build a prototype and see if you can achieve your aims
3. Change storyboard.

Although Opus does have DB actions that can do various things, from past experience, I suggested sticking with DB scripting.

With regards to your data protection, Canada does a various laws governing what you can store and how it must be stored:

http://www.privireal.org/content/dp/can ... canada.php

If you are going to use MS Acess then only V2007 has a decent level of encryption acceptable by most counties standards. The alternative is to encrypt the data prior to writing it to the DB - something made a lot easier thanks to DW DLL implimentation (search 1crypt on forum).

Other DB systems such mySQl have built in functions that can be called via the SQL to encrypt the data.

Mack

I am sorry to hear that i have created you some grief , i hope you work out the bug with ease...

Al

[quote="mackavi"]Having created quite a few DB interfaces using Opus and fixed several more for other people I have to recommend several things:

1. Storyboard your DB application and note on it the neccessary interactions.
2. Build a prototype and see if you can achieve your aims
3. Change storyboard.

Although Opus does have DB actions that can do various things, from past experience, I suggested sticking with DB scripting.

Hi Mack,

You are always thorough with your answers and thanks for that . I am a novice to scripting ( thanks to Sandyn and U ) for helping to atleast start this move to scripting . So should i use the scripts that are in the side bar in OPUS or get scripts from the net ? . Like i said i am still NEW and yes i do understand the process on how to make my own , but somtime i just get stuck and need to be able to look at an exqample to get the right path going.....

The pub i am planning really need to have the client enter the data at their end , so i guess i am stuck with using access 2007 . I guess for now i will have to forge ahead and give it ago , and i really enjoyed your database example you made with Captivate , that was very well understood......

Al

Cheers Al,

Can't say that I every really use anything but the objects tab on the sidebar. I was supprised to find, thanks to Sandyn, that there is a ready built volume control - so am not the best person to advice on that.

The are, or should be some decent examples of DB scripting in the forum post and the Script help in Opus in normally quite good. I'd suggest creating a sample DB and just getting Opus to read in values to start and then see if you can add some data.

As for why you'd have to use Access 2007, I'm not sure I understand this comment.

I'd forgotten about the capitivate example. I'll have to dig it out and remind myself. I'm actually in the middle of looking at using an LMS to provide online lessons include teaching OpusScript.

Mack

[quote="mackavi"]Cheers Al,

Can't say that I every really use anything but the objects tab on the sidebar. I was supprised to find, thanks to Sandyn, that there is a ready built volume control - so am not the best person to advice on that.

The are, or should be some decent examples of DB scripting in the forum post and the Script help in Opus in normally quite good. I'd suggest creating a sample DB and just getting Opus to read in values to start and then see if you can add some data.

As for why you'd have to use Access 2007, I'm not sure I understand this comment.

Well Mack sign me up for any teaching class you put together as i have already seen your style and find it easy to understand . The reason for Access 2007 is the need for privacy of the database .. The example you did with Captivate was excellent and in the forum i Sandyn pointed me to you even mention you made a mistake in the captivate example .

If you ever correct it let me know as it was a great example to follow..

Al

Cheers Al,

I'm hoping to get the LMS online and setup with Lesson One of Module One today. I was going to request some beta testers but as you've already thrown yourself into the pit, I'll mail you a course key.

If I can find the DB project, I'll get that uploaded as well.

Mack

OK ,

ready when you are Teacher

Al

Hi Al,

As promised, the beta of Interaktiv's LMS is online - but still needs tweaks, if you want to try the first Lesson of the Introduction to OpusScript, register at:

http://www.lms.interaktiv.co.uk

and use the following course key.

QWERTYUIOP12345

There's a forum board attatched to the module where you can post questions and ideas.

Mack