>>I've tried that but got confused over what I had done in designer and what I hadn't. How do you keep track of the designer work, like what fields are updateable, etc. (aside from the Create View...SQL)? Maybe there's a way to get the designer 'setprop' code?
>How about the READMETHOD method?

What I meant is that if I use the designer for part of the create view process, I'd like to be able to dump out all that code (including all setprops) and paste it into my app, where I could then tweak it as needed. There may well be an easy way to do this, I just don't know about it...that would be a real convenience, if anyone knows how to to this?

>
>P.S. I found that part of my problem was that I had not marked the key field as updateable in the View Designer. It defaults to NO.

Yes, that's a good idea (s). Basically you just have to play with the view designer (or code) awhile to find out how to get it working correctly...it's not greatly difficult, but there's a bit of a learning curve.