Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 16 MAY 2013 07:10:53PM Jim Mabey wrote:

I checked with Bob and Jared and was advised that AREV32 no longer supports the DBASE bond. I have some tables I write data to so that a Crystal Report can access them to create PDF files which I then allow users to view via an OI web app.

I recreated the DBASE tables in one of my MS SQL server databases. I then created a SQL Connection and SQL Dataset. After doing this I am able to edit data in AREV32 in these tables and I can see the changes in MS SQL server. I can also update the data via SQL and see the changes via AREV32 EDIT. I am also able to do a "listdict" on these and see the fields.

However, if I try to "list" the tables, I get an error "SYS1000: Error Loading Program: LIST 2" and AREV32/OI complete crash back to the windows desktop.

Also, if I try to write to the tables via a standard "WRITE" in AREV32, I receive an error message on the screen "FS330".

I'm running AREV932 in demo/trial mode.

I granted full permissions on these tables in the SQL SERVER database.

I also tried both OS auth as well as an explicit user name/password.

I have permissions from SQL Query analyzer and like I said, I'm able to change the data via an "EDIT" under AREV32 so I don't understand what the issue could possibly be…

Please advise if anyone has any tips.


At 16 MAY 2013 09:02PM Jim Mabey wrote:

I just noticed that "SORT" works under AREV32 on these tables whereas I get an error when I use "LIST". Note also that "LIST" appears to work fine on normal LH tables.


At 16 MAY 2013 10:01PM Jim Mabey wrote:

The FS330 error happens when I try to do a "CLEARTABLE" on a SQL table.

I wrote a routine CLEARTABLE_SQL that I have do a select/savelist/readnext/delete on the SQL table as a workaround.

So, I got past this issue, but if anyone has a fix for how I can use the "LIST" instead of "SORT" and for how I can use the "CLEARTABLE" instead of my custom CLEARTABLE_SQL then by all means, please share.

Thanks,

Jim Mabey

951-733-1334


At 16 MAY 2013 11:27PM Bob Carten wrote:

Hi Jim,

The fs330 is a ug in the SQL connector. It is fixed in the 9.4 relase of OI.

I will look at the Arev LIST problem.

- Bob


At 22 MAY 2013 08:50PM Jim Mabey wrote:

Hi Bob,

Thanks. My CLEARTABLE_SQL approach of SELECT/READNEXT/DELETE works fine if there are only a few records in the table, but horribly slow when there are thousands.

I'd like to find an easy way to just do a simple "DELETE * FROM tablename" directly against the SQL table.

I've done XO stuff in OI, but don't want to have to store/use the credentials.

Is an easy way I can pass through a SQL command from AREV32 or even from OI where I could use a CTO_GUI_FUNCTION call to execute the OI command from AREV32?

When will version 9.4 be available?

Thank you,

Jim Mabey


At 23 MAY 2013 08:20AM Bob Carten wrote:

Hi Jim,

There is a program named DSBFS_EXEC_SQL which will let you pass SQL statements directly.

sql_statement = "update authors"

sql_statement := " set state = 'TN'"

sql_statement := " where state = 'UT'"

result = ''         ; * result of any select

demote_levels = ''  ; * result will come back as rm rows / fm cols, demote levels will change to fm/vm or vm/svm,

                    ; * Pass 0 for rm/fm, 1 or null for fm/vm, 2 for vm/@svm                    

param_names = ''    ; * Stored proc or param  query? this is an fm delimited array of parameter names

param_vals = ''     ; *  associated array of parameter values

param_types = ''    ; *  associated array of parameter data types

result_code = dsbfs_exec_sql(connection_name, sql_statement, demote_levels, result, param_names, param_vals, param_types)

If result_code eq -1 Then

	Msg(@window, 'Unable to execute command ' : Quote(sql_statement) )

	Return ''

End

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/c3a0cb795690d1717362e9ba4.txt
  • Last modified: 2024/01/04 20:57
  • by 127.0.0.1