Help with an Opera 16 error

Hi all I know opera 16 is no longer supported but I was wondering if anybody has come across the following error?
they get the message when added any supplier details to any product. they also get the same error when on a supplier and try to add the product.
I have check DSProd and this table looks ok.
I have found that they can add the supplier details if they do it on the fly when creating a purchase order.
I think on the update it is checking a different table but I can not work out which table and what it is checking.
Has anyone got any ideas ?

Any help much appreciated

Andy

2011-10-27_CH-Stammtisch_2.pdf

Find more posts tagged with

Pegasus - Partner General Discussions

Comments

unknown

Check SYSTEMSEQLOCK for any semaphore locks.
Check for open files/locks on server > computer/share management
Try adding a new record manually using Foxpro (ideally FPW 2.6).

andy-parker

Thanks for the reply

I have brought their data back to office set up new install and added their data, ran UDS and reindex tables, still get the same error. I can append a blank line to dsprod and delete and pack the table. if I manually add a line in I can then amend the line in opera I just can not add a new line thought opera except by using the purchase orders

unknown

Weird! So for the avoidance of doubt, you've tried it with a fresh Opera 16 install and fresh SYSTEM folder? Any bespoke involved? Might be worth running foxfix on DSPROD just in case.

andy-parker

that what I thought, yes new system folder they do have bespoke but I did not bring any of that over just there data. I have ran foxfix on all the files. it has been working ok until Friday and they say "they have not had a crash" I think it could be a softlock in a table, but not sure which one or a flag that it is checking on saving. What I really need to be able to do is to trace the error thought the code to see what it is checking to trigger the message

ric

I would check the tags in the index are in the correct order. I have occasionally seen the order getting swapped e.g. DSPROD2 first in the list. If the code is doing something like SET ORDER TO 1 then it would be on the wrong index and then the SEEK finds a record because it is not using the correct index.

colin-avey

dug out a few antiques including old devdg267

looks like SQLOCK, SQG_ADDLOCK_L and
SQADDREC all can produce this message. all act in a similar way by checking SEQLOCK.lk_code for matching key.

something like

IF SEEK(PADR(lk_coid+lk_alias+lk_key, 30))
USE
DO sqmsg WITH '145,158'
SELECT (lk_alias)
RETURN .F.
ENDIF

May be a red herring but,

potential issue I can see is lk_code only c(30) and key checked is going to look like lk_coid+lk_alias+ds_cnref+ds_account+ds_supref, so may cause problem when adding similar records in a browse list.

can you have SEQLOCK open in fox while adding record in Opera with error displayed and see contents

HTH
Colin

andy-parker

I just for a test I zapped dsprod and tested again and all working ok I then append the lines back into dsprod and get the same error. so there must be a problem in the data in dsprod

andy-parker

I all thanks for all your help I have now found the issue I had one line in dsprod that did not have a ds_cnref - remove that line and all working ok

unknown

Well found Andy. That's one for the knowledge base! I expect the same problem could occur in Opera II/3 as well.

0911060553270289.pdf

Copyright © 2025 Infor. All rights reserved.