>Doug
>
>Here is the relationship:
>
>Client Table (Fox4Dos table - for your info)
>Allocation Table (VFP Table)
>
>Client.Cl_Ref => Allocation.Cl_Ref
>
>This is a one-to-many relationship, and I'm sure it's setup OK.
>
>Kev
My copy of the "Hackers Guide To Visual FoxPro" is at home, and I will have to wait until this evening to take a look at it. But there is a great example and the explanation for the ********** stuff, in the relations section, just in case you have a copy of the book. It is all to do with the type of relation set in the data environment and has nothing to do with numeric overflows or field lengths.
I learned more about FoxPro from using this book and its examples that I think I had learned "in the trenches", but it is especially helpful for those less frequently used functions that one doesn't just keep at the top of their heads.
MSCE, MCSP, Microsoft Channel Partner
Relax, Boss. We will meet the deadline! What? You want to add MORE? What do you mean, Over Budget?
Opinions and comments are the sole responsibility of the sender, and accuracy, correctness, or pertinence is considered coincidental.
