>>Something else is wrong. I'm actually using couple of .dbcs to keep the updatable views on free tables which reside in another directory, and define them programmatically, starting with what GenDbc gave me. There was a bug of a kind in what it produced - I've had free tables with the same name in different directories, and GenDbc didn't include the proper path to them in the generated routine (namely in the "from ..\otherdir\table" part of the SQL Select, the "..\otherdir\" part was missing), so I had to fix it. It may be doing other things, too. Once these quirks are taken care of, it works fine.
>
>You have defined the problem just right. The DBC can't retain the path for free tables so if the table is not in the current directory sent updates doesn't work. You can't even force the path by using CURSORSETPROP('tables'). I think you're right, it's a bug.

But the bug isn't in the .dbc - it works for me. It's the GenDbc which incorrectly generates the view building code. I ended up defining the views in code, and this (gendbc + manual fixes) code actually creates a .dbc with view definitions, and they work fine.