Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Tables not forming a relationship properly
Message
 
 
To
16/07/2003 11:07:13
Brian Weber
Ohio Department of Development
Columbus, Ohio, United States
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00810631
Message ID:
00810687
Views:
33
I am not asking the right question. What are you doing on the form that you are expecting to update data in all the related child records? How are you displaying the child records? Usually a grid is used to display all the child records of a parent table. Are you using table or record buffering? If so, are you issuing a TableUpdate() which would save the data?

Updating a single record in a table does not automatically trigger updates in a child table with multiple child records with respect to the parent record.

>Of course I can give more detail. So here goes nothing....
>
>The project that I created as a learning application is a phonebook app. This is my first venture into FoxPro, but not data bases. I have used SQL and Access before. The main differnace is I wrote that code in ASP, not FoxPro. So its not like i have never set up a data base and got it to work before. Back to the project, it is just a form, two tables, and a spalsh screen that brings you into the working form. Everything works except one small( i use the term lightly) problem. Thats why im here lookin for an answer.
>
> I have the two tables hooked up with a parent child relationship using a primary key set up. I have the form designed to update the information in each field based upon actions by the user. These actions can be dropdown/combo boxes and lists. Everything works just fine for any information being pulled from the parent table, but alas the fields from the child tables are stuck there. It doesnt update them at all. What im looking for are potential reasons that it isnt updating. I have every possible action on the page(s) refreshing the data, and i also have made sure that it is pointed to a valid table and field. I know that something in the child table is related to the primary key in the parent, simply because i created both of them myself, and have look at them. I'm also possitive that there are no repeats of the primary and foriegn keys for each table.
>
>Any ideas?
>Brian
Mark McCasland
Midlothian, TX USA
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform