Digital Workshop

Hello,

Don't know if anyone can help, but had quite a frustrating problem.

I've got an access database connected to my opus v.6 publication.

To start with, I was able to read data from the database, search records, update current record, add and delete records.

BUT

Each record in my database has 150 fields.

When I update just a few fields at a time, I manage to do so.

But if I try to update say 100 fields at once, NONE of the new data is updated into the file.

Is there a limit on how many fields Opus can cope with?

Has anyone else encountered a similar problem?

Hi Paul,

Did you write the access and update into a Opus script? If so pls show a copy of the script.

Cheers

Hi,

I just used the options in Opus - no scripting used at all. Think I may have actually (after around 6-7 hours) have found a cause - that when you have a variable to update the database with, then if the variable is blank, this stops the entire update working. At least, ensuring none of the variables was blank has stopped the error for me. Has anyone else any experience of a similar problem?

I've created several database applications, and I can't remember having problems like this. I tend to use text fields, accept nulls and I use a space (" ") for any blank fields written to the database.
When you say 'when a variable is blank' how have you set up the variables??
and how do you write a 'blank' to the database??


Sandy

Hi

I've created a new variable, either as a string or as a number, but not put any value into it. Then have a text input box for users to input a value to it. If they choose not to, then the variable is still blank. When I update current record, I asign the variable to a field, so that is how I can end up with a blank value being created for a field.

Thanks

You should use scripting for database as it is much easier to do for large field updates and easier to diagnose as we can view your SQL script and see if it is correct. The scripting engine in Opus is it's strongest feature and makes developing applications extremely easy, especially for repeat actions.

The only problem I have with database is having more than one user connected to the same Access Database from multiple computers. But that appears to be more of an Microsoft issue than anything else.