greendot2
asked on
Can't get IndexFieldNames to work
I'm working with D3 and FoxPro tables.
I clearly have many indexes on my table. I can see them in the DBD as well as the DB Explorer, AND I can use them in the table.IndexName property.
That all works fine..
But when I do: table.IndexFieldNames := 'field1;field2';
It barfs on me and says that it can't find the index.
Am I doing this correctly?
To actually state what I am TRYING to accomplish with this, I have a two tables. One is on a CD and one is on the hard drive. Every month the user will get a new CD and I have to update the hard drive table with new records... BUT I can't overwrite any previous records.
This condition is based off of two fields: ELEMENT and TYPE
If the same element and type are on the hard drive, the record is not copied over. Pretty simple..
So I have an index on both of these fields. I tried making one index with both fields but it seems FoxPro/DBASE doesn't let me do this. :(
Using the FindKey([value]) allows me to jump to element number really quickly and see if it's there. But since there can be multiple elements with different types and this only gives me the first one, I need to find a way to jump to the given type as well.
So I'm trying to make the TTable use two indexes and hopefully FindKey([element, type]) will work.
Will it?
Is there an easier way to quickly tell if a record is in a table based on two fields? I need this to be quick because there are possibly hundreds of thousands of records on the CD that need to be updated.
Thanks,
joe
I clearly have many indexes on my table. I can see them in the DBD as well as the DB Explorer, AND I can use them in the table.IndexName property.
That all works fine..
But when I do: table.IndexFieldNames := 'field1;field2';
It barfs on me and says that it can't find the index.
Am I doing this correctly?
To actually state what I am TRYING to accomplish with this, I have a two tables. One is on a CD and one is on the hard drive. Every month the user will get a new CD and I have to update the hard drive table with new records... BUT I can't overwrite any previous records.
This condition is based off of two fields: ELEMENT and TYPE
If the same element and type are on the hard drive, the record is not copied over. Pretty simple..
So I have an index on both of these fields. I tried making one index with both fields but it seems FoxPro/DBASE doesn't let me do this. :(
Using the FindKey([value]) allows me to jump to element number really quickly and see if it's there. But since there can be multiple elements with different types and this only gives me the first one, I need to find a way to jump to the given type as well.
So I'm trying to make the TTable use two indexes and hopefully FindKey([element, type]) will work.
Will it?
Is there an easier way to quickly tell if a record is in a table based on two fields? I need this to be quick because there are possibly hundreds of thousands of records on the CD that need to be updated.
Thanks,
joe
background info : version of bde?
As Zif said, upgrade to BDE 5.0/5.01 maybe a solution, since 4.51 yet have no direct support for foxPro tables.
hi greendot2,
you can use a query to insert the records based by your fields.
i.e
insert into destinationtable select * from your Sourcetable where field1||field2 not in (select field1||field2 from your destinationtable)
if one or both fields numeric-typ then you can convert it to string by use of
cast(field1 as character)||field2
or
cast(field1 as character)||cast(field2 as character)
it works with paradox (foxpro should work also)
field1 and field2 must concanated to build a temporary primary field.
depends on the count of records the query can take time.
meikl
you can use a query to insert the records based by your fields.
i.e
insert into destinationtable select * from your Sourcetable where field1||field2 not in (select field1||field2 from your destinationtable)
if one or both fields numeric-typ then you can convert it to string by use of
cast(field1 as character)||field2
or
cast(field1 as character)||cast(field2 as character)
it works with paradox (foxpro should work also)
field1 and field2 must concanated to build a temporary primary field.
depends on the count of records the query can take time.
meikl
ASKER
I'm using BDE 4.51, and this was the one that added native FoxPro drivers. I have 4.0, 4.51, and 5.0 and tested each one. 4.51 is the most stable. We tried 5.0 but the LocalSQL engine hung more times than it worked. (only on the foxpro tables, it worked fine with Paradox).
I've managed to get it working with a filter, without much of a performance hit. I'll try inserting them with SQL today and see how smooth that is.
Thanks,
joe
I've managed to get it working with a filter, without much of a performance hit. I'll try inserting them with SQL today and see how smooth that is.
Thanks,
joe
hi greendot2,
have you test it? For assistance response!
meikl
have you test it? For assistance response!
meikl
Hello?
ASKER
Go ahead and post an answer.. I'll give you the points.
I never actually got around to finishing this problem.
I'll pick it up in a few months.
I never actually got around to finishing this problem.
I'll pick it up in a few months.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.