Network Version of Valentina

[Ivan Smahin]

Hello Don,

Saturday, February 11, 2006, 12:10:18 AM, you wrote:

> OK, I don't think I'm explaining this right.


> Data in original Valentina 1 DB
> Words Table
> RecID     Word
> 1         word1
> 22        word1
> 34        word3
> 56        word4
> 71        word5

> Data in new Valentina 2 DB after coversion
> Words Table
> RecID     Word
> 1         word1
> 2         word1
> 3         word3
> 4         word4
> 5         word5

> Exported Data for the WordsScore table of V1 database
> RecID,Score
> 1,25
> 22,100
> 56,34
> 71,0

So - there is no objectPtr linked WordsScore to Words?
Just some internal app logic based on "unchangable Word's RecID" idea???
Then you've got a problem.

> The Words table is not going to change after the database is
> delivered to the end user. Let's say we have a table named
> WordsScore. This table has two colums one is a link to the RecID of
> the Word table and the other field has the score for that word. So
> lets say that I export the data from the WordsScore table in V1
> database. Importing this data in the WordsScore table of V2 database
> would have an incorrect RecID. I cannot link by the Word field in
> the Words table because we can have duplicate words with different RecIDs.

> Does this make sense? I hope I did a better job at explaining this time. Thanks.

Ok seems the picture above is not finalized.
As  far  as  I  get it - you have one more ObjectPtr field here - link
WordsScore to Words? So you had:

Exported Data for the WordsScore table of V1 database
Score    OPtrToWords
25      1
100     22
34      56
0       71

So after Convert_1_2 you will see:
Exported Data for the WordsScore table of V1 database
Score    OPtrToWords
25      1
100     2
34      4
0       5


BTW,  We  have  just  fixed  some  glitch with Convert_1_2 which makes
possible  to  convert  your database. (It was "broken" v1's ObjectPtr -
no target table.)


-- 
Best regards,
 Ivan                            mailto:ivan_smahin ÎÁ valentina-db.com