Ok, the problem now may rest in peace.
Here is what is was for lurkers:
My colleague wrote a generic utility to create database using Excel files with tables definitions. He also had a program to generate view script, so we have view scripts for all our views. Now, we changed the table name but we didn't change the field name at that time. So, he generated view scripts and ran them. Then lately we changed the field name to match the table name. However, I think, we didn't fix this view script, so it was still wrong and was saved wrongly in the database, though if we open that view in the view designer, it was correct. This is a little bit of a mystery. Anyway, I fixed the view script and re-ran it. Now everything is fine.
>>Hi everybody,
>>
>>Quite recently we made structural changes with our Database. We renamed table Queue_Profiles into Employee_Queue_Profiles and therefore we also renamed PK field from cQueue_Profiles_Pk into cEmployee_Queue_Profiles_Pk. We made all necessary related changes. The database is good and running. However, when we use GenDBC to generate a program, we get this weird result
>
>Maybe it's finding the deleted records in the database? Backup, open dbc exclusively, do the cleanup, try again.
If it's not broken, fix it until it is.
My Blog