Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

View Problem

Status
Not open for further replies.

rgw

Technical User
Sep 14, 2000
70
US
I'm having a problem with an updatable view. It contains a view of fields from 4 different tables (3 in a .dbc and one free).

If I code the sql myself joining the tables everything links together but when I try and duplicate the results in a view it gives me an error saying it can't find one of the fields. Putting them all in the .dbc made no difference.

Any thoughts?
 
Rick:

Thank you for the help. I'm using 6.0 never having bothered to use 7.0 but will receive 8.0 next week. My problem seems to be when I bring in that third child table into the view. Do you think 8.0 solves this problem or should one go for the add-in?

many thanks
 
Rgw,

My problem seems to be when I bring in that third child table into the view

How are the child tables related? In general, the view designer works fine with parent-child-grandchild relationships, but it stumbles when the parent has two sibling children. In those cases, you probably will have to code the view manually.

As far as I know, VFP 8.0 does not change that.

Mike


Mike Lewis
Edinburgh, Scotland
 
rgw and Mike,
Actually the 8.0 View designer has been greatly improved - including handling 2-way changes in the view SQL window. It's rumored that the VFP team "borrowed" some of the ideas implemented in the GeeksAndGurus ViewEditor.

Rick
 
Rick/Mike/RgBean

Many thanks. The problem seems to persist in View Editor. As I build up the query it works fine with a parent and two child tables but blows up when I add the third child. I'll wait for 8.0 to arrive in the mail and see what happens there. I think I've created this problem as a result of trying to make my tables more efficient by stripping off credit card transactions into a separate file. As a result I've made my parent table smaller but created problems elsewhere.

When I create the regular sql statement in a program it all works as expected. Shows what you expect to see but doesn't do much for automating the update procedure which is what I was looking for.

Anyway, many thanks
rgw
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top