Inconsistency in BSV when applying to production system

denisv

I am applying a new BSV to a production system and it is giving an error stating that the business space has inconsistencies and to check it.

However it does not give any such message in the designer. Is there anything else that could cause this ? Ver 2.2 Build 937

aware_support

The reason is that you are using two different databases. A BSV may be consistent if used for one database and not consistent if used for another one. The reason is that there are certain keywords used in one database but not the other one. For example, "Year". You just need to rename all offending attributes into something that does not have conflicts in either database, for example "ProductionYear" instead of "Year"

denisv

Thank you I will investigate. I have added several fields and I am running against Derby while the production version is against SQL.

denisv

Can you advise if long field names might have the same impact. I don't think I used any keywords in field namdes but willl check, however I may have used long field names.

aware_support

Yes, long names might have the same impact. You may consider making them shorter if they are very long.

tford

denisv,

I had this happen a couple of months ago also.

I am running derby locally & MySql on a production server also. I transferred the problem bsv to the production server via FTP instead of using the "upload version" option. Then I did an integrity check on the server while logged in via remote deskptop.

Tom

denisv

Thanks Tom,

I have only used the upload version. I suspected my issue was with long field names but have since discovered I have (foolishly) named a field Duration. Whilst working fine in Derby, I believe this could be the problem.

Next dilema is I've lost remote access !!! Neither you nor Aware can solve that one ! So I'll await connection to test if ok.

Thanks