>Hello All.
>
>This one is driving me crazy (OK - I know it is a short drive). I am modifying a Visual ProMatrix application and in one form, if I change the primary key and save it, the changes are correctly cascaded to all the child tables. However, nothing else works after this change of PK. Every time I try to REQUERY() a view, it gives me back the complaint in the title. The goofy thing is that it only does this when running against local views. When I run the same code against remote views, everything is peachy keen.
>
>Also, if I open the data session window (when running against native data), I see a bunch of extra aliases like 'W44', 'W39', etc. that are being opened. DBC() returns FuneralCase.DBF (which is indeed the main base table for the view I am trying to requery. I have confirmed that CaseNo really is a column in the table.
>
>If I do not change the PK and just edit information, it is able to "see" the column CaseNo with no problem. It also has no problem cascading changes of PK when running against SQL Server.
>
>One more piece of information that might be relevant: someone had originally named the table 'Case'. As you might guess, this caused a lot of problems, so I renamed the table to FuneralCase.
>
>Anyone have any ideas?
>
>TIA

How this PK is defined in these tables and why are you changing it? Normally you would avoid changing PK.