>Cetin,
>
>I have done as you suggested. I used GENDBC on my DBC file. It crashes with an error on line 500. When I look into GENDBC.PRG, I can see that line 500 is the command COMPILE. So, GENDBC has created the PRG file, and is now compiling it.
>
>The error says that a line is too long.
>
>If I understand this correctly, it is saying that some line in the PRG file generated by GENDBC has a line that is too long. Online help says that lines must be less than 8192 characters long!
>
>Do you know of any way to determine which line in the PRG file was found to be too long? If I open the PRG in NOTEPAD, I can scan through the file, and verify that no line is physically longer than maybe 150 chars. So, the error must be a "logical" line, i.e. wrapping, with some string terminator missing. Such an error is very difficult to see.
>
>Thanks again for your help.
>
>Jim

I think the problem may be with a stored procedure. Do you have auto-generated RI code? How big is your database?

We had originally native RI and lots of times got internal consistency error for the database. We then switched to an RI based on Doug Henning's code, which is slower for multi-record updates, but produces compact code and gives us flexibility to turn it on and off.