I'm having really big problems attaching tables from different directories with the same application (Previous discussions: "How to recover from SYS1302, SYS1303 errors" posted on 12/07/98 and "More info about the SYNCDB" posted on 12/09/98. The results from these discussions are the following:

1. Use of the SYNCDB form: this is OK from the developer's environment but I can't deploy it to the users because my application is totally in spanish. Besides, I think the fix of this error should be transparent to the the final user.

2. Use of the SYNCDB function: I received the SYNCDB code from Cameron of Rev. Soft. but I had the next compiling erros:

FS200: The "REV_BP" table is not available.

SYS1215: The compilation has failed.

and after commenting the "$insert Rev_BP, SysCommon" line, I got the next compiling errors:

B102:Line 12.Illegal Statement:POINT VOLS TO SC_ARRAY_VOLUMES(0).

B102:Line 13.Illegal Statement:POINT VOLFILES TO SC_ARRAY_VOLUMES(3).

B102:Line 14.Illegal Statement:POINT FILES TO SC_ARRAY_TABLES(0).

B102:Line 15.Illegal Statement:POINT FILEVOLS TO SC_ARRAY_TABLES (1).

B105:Line 55.SC_ARRAY_TABLES has not been dimensioned or declared as a function.

B102:Line 55.Illegal Statement: SC_ARRAY_TABLES(I)=DELETE(SC_ARRAY_TABLES(I),IFILE,0,0).

B105: Line 65. SC_ARRAY_TABLES has not been dimensioned or declared as a function.

B102: Line 65. Illegal Statement: SC_ARRAY_TABLES(I)=DELETE(SC_ARRAY_TABLES(I),IFILE,0,0).

SYS1215: The compilation has failed.

3. Upgrade to OI 3.7: I already did it and the problem still continue.

I am really desperate about this stuff. We have a jan 15th, 1999 deadline to finish this application and we are hung up on this stuff.

I think the best solution is that somebody from Rev. Soft. can send me an error free version from the SYNCDB function, so I can freely use it at the points of my application where errors are happening.

I'm using OI 3.6.

I'll really appreciate somebody's help (specially from Rev. Soft.)

Thanks in advanced…

Ruben,

I'm having really big problems attaching tables from different directories with the same application (Previous discussions: "How to recover from SYS1302, SYS1303 errors" posted on 12/07/98 and "More info about the SYNCDB" posted on 12/09/98.

First, have you looked at SYSPROCS/SYSERRORS_1000? That is the record that defines the errors SYS1302 and SYS1303:

equ sys_invalid_object$ to "SYS1002"

equ sys_load_overflow$ to "SYS1003"

The first represents improperly formed object code. It is only set by RTP27, the program loader. The second represents a full program cache. Again, it is set by RTP27.

1. Use of the SYNCDB form: this is OK from the developer's environment but I can't deploy it to the users because my application is totally in spanish. Besides, I think the fix of this error should be transparent to the the final user.

As I said, in 3.7, the SYNCDB logic is built-in. So if 3.7 does not fix the problem, then SYNCDB is not the answer.

2. Use of the SYNCDB function: I received the SYNCDB code from Cameron of Rev. Soft. but I had the next compiling erros:

As I mentioned when I posted the source, you cannot compile SYNCDB. It requires the system compiler.

3. Upgrade to OI 3.7: I already did it and the problem still continue.

See above.

I am really desperate about this stuff. We have a jan 15th, 1999 deadline to finish this application and we are hung up on this stuff.

Ruben, is the Attach_Table problem always reproducible? If so, I am guessing that:

1) One of the system SSPs is corrupt. Easy to fix - copy the records from a clean SYSOBJ over yours

2) One of your MFS's is corrupt. Try re-compiling them in 3.7 and see if you get an error.

3) Try using alias_table instead.

4) Make sure you Set_Status(0) before calling the SSP.

5) What table names are you attaching? What dbid?

Cameron Purdy

Revelation Software

OK Cameron. Thanks for all the information. I'll work on it and I'll send you the results afterwards. Do you have a personal email where I can send you my comments?

Hi Ruben,

If you need to post information that you do not want to be public, use the Works Private Online Discussion. Otherwise I would encourage you to continue posting the issue here since other developers using OpenInsight may be able to help you as well.

Cameron Purdy

Revelation Software

View this thread on the Works forum...