Digital Workshop

My Opus Publication only let me write 64 entries to Microsoft Access at a time???
What on earth is the reason for this?

Some suggestions.

1. verify you have not left-in some (max 64) Access argument from testing efforts.
Similarly, check that you do not have some Opusscript counter limiting results in a "for" statement.

2. try the Opus Pub entirely on another, perhaps older-Window machine.

3. track/observe variables in your script at each step/cycle... showing what's going on using Debug.trace().

4. try your Access WRITE statement directly within MS Access's console (or whatever its called... for report or queries)


MS Access itself can handle thousands of rows, and write operations should not be limited.... other than by memory or by given instructions.

Hi Lar 123,

Thank you for you responds, I check my code and see no counter limits or Opus script that prevents me to write more than 64 at a time (attach is a screenshot of all the "steps" when the user clicks on a button) and the script is as follows:



Everytime the user click the next button the script above is excuted, the problem is my publication is over a 100 pages long and only the first 64 pages details is captured, the rest is not insert into the database at all.

Correct me if I am wrong on what you mean by "entries". I interpreted that as writing 64 records (or rows). And according to your explanation of Opus Page layout and User-clicks, database write/insert is done once-per-page (not 64 records at a time). It seems you must get to page 63 or 64 and then you cannot write to database from Opus pages that follow??? (Could be a more general error on that later opus page?? Does Debug.trace reveal anything there? ).

BTW, ODBC Data Sources (settings in windows administration) has some things to help you:
* you can turn ODBC logging ON --- to perhaps get more details.
* Windows ODBC drivers used may need to be looked at.
If you are running 64-bit windows and the Opus Pub is a 32-bit program, you may need to check your drivers setup. Although it seems you established a working connection somehow. (google: SysWow64 odbcad32.exe)

ETA: If you are opening the DB, writing a record to it, and closing it --- all from one Opus Page (then repeating on next pages), ODBC default timeout should not be an issue.