Navigate related records

[Bob]

Hello:

I'm building a simple windows database application that has two tables with
One to One relationships on MS Access tables.

I know what your thinking. Why not just use one table? because MS Access
has a field count limitation of 255 and my table would have 327 fields so I
have no choice.

I'm using two Data adapters that generate a single DS with a relationship
build on the ClientID fields.

I dont' wish to use a datagride because the customer doesn't want it.

I can't figure out how to make my app populate the fields in my form with
the child data when the dataset loads and moves to the next record.

Below is what I have and it works ok:

Me.BindingConte xt(objdsClients , "ClientsMain"). Position =
(Me.BindingCont ext(objdsClient s, "ClientsMain"). Position +
1)Me.BindingCon text(objdsClien ts, "ClientsPage01" ).Position =
(Me.BindingCont ext(objdsClient s, "ClientsPage01" ).Position + 1)
But as you know, it can quickly cause problems later if the child table
doesn't have a child record added for some reason like a power failur or
something else.

I built the relationship in Query Designer

Any help would be appriciated

TIA

Bob

[Bob]

Cor:

ok, I tried it and got the same runtime error

An unhandled exception of type 'System.NullRef erenceException ' occurred in
WindowsApplicat ion1.exe

Additional information: Object reference not set to an instance of an
object.

Same as I get in my project

Thanks again

Bob

[Bob]

sorry, the code highlighted is

ds.Tables.Add(d tCountry)

Bob

[Cor Ligthert]

Bob,

I tried this sample when I send it, and now again, I had/have not any error.

Can you paste it back to show what you made from it?

Cor

[Bob]

Cor:

Once again, I appologize for the confusion.

these early mornings without that first cup of coffe.

Me in my infinite wisdome, I forgot to past it into notepad first.

Thanks for all the help and sorry for all the false alarms.

I'll try to implement this into my project

Thanks again

Bob

[Bob]

Cor:

I appriciate the help you have given me but now that I look at it, I already
had a form of that. Thats based on row position.

That won't help me because thats not 100%. A simple power failure can throw
that off too easily. If data gets entered into the parent table and for some
reason the users stop entering data into the child tables, power failure,
system hang etc ...

See where I'm going?

I need something based on real relational concepts. I spent money on VS
becaused it advertised that but I'm thinking I'm better off with what I know
(VS6).

Any other suggestions?

Thanks again

Bob

[Cor Ligthert]

Bob,

That won't help me because thats not 100%. A simple power failure can
throw that off too easily. If data gets entered into the parent table and
for some reason the users stop entering data into the child tables, power
failure, system hang etc ...

No, because that is in any concept the same.

AFAIK, can you not update easily a joined table, that you have to do table
by table using AdoNet.

Cor