sloppyjoe73
asked on
Rewriting DAO query as ADO
Does anyone happen to know what the ADO equivalent of this DAO query would be?
Database.Execute "SELECT name, address, address2, now as entry INTO [dBase 5.0;DATABASE=C:\DBF].[EXAM
This is just a sample, as the actually query is about 7 lines long, but it includes all the elements of the original. I've tried many things, but just one error after another. Many thanks and 250 points to the first person that can help solve this problem!
Database.Execute "SELECT name, address, address2, now as entry INTO [dBase 5.0;DATABASE=C:\DBF].[EXAM
This is just a sample, as the actually query is about 7 lines long, but it includes all the elements of the original. I've tried many things, but just one error after another. Many thanks and 250 points to the first person that can help solve this problem!
ASKER
Actually, I should have called it [MyTable].[Exported]
[MyTable].[Exported] is a boolean (yes/no as it would be called in Access) value. Once the record gets exported into the DBF, the "exported" field gets set to true so that the same record isn't processed again. The program keeps a short history of records in case one needs to be resubmitted in the future.
I'm actually going through the query now removing the fields one at a time. It seems to work fine when I remove all but the first few fields. Maybe it isn't the syntax after all.. just a problem with one of the fields. Gonna go check my fields.
[MyTable].[Exported] is a boolean (yes/no as it would be called in Access) value. Once the record gets exported into the DBF, the "exported" field gets set to true so that the same record isn't processed again. The program keeps a short history of records in case one needs to be resubmitted in the future.
I'm actually going through the query now removing the fields one at a time. It seems to work fine when I remove all but the first few fields. Maybe it isn't the syntax after all.. just a problem with one of the fields. Gonna go check my fields.
ASKER
Looks like it's being strange with some of the fields. Since I'm not in control of the program on the other end of this DBF file (written in FoxPro), I'm having to insert some empty fields into the dbf as to not make the program on the receiving end cranky. I'd much rather just leave them out, but the program on the other end is expecting them to be there. I've been using syntax such as:
SELECT normalfield, '' as blankstringfield, 0 as blanknumericfield
For some of the fields this works just fine, but for others it gives me the error "Field will not fit in record." If I use a blank field from the access database in place of '', it works just fine. i.e.
SELECT normalfield, blankDBfield as blankstringfield, 0 as blanknumericfield
I would think it would see '' (two single quotes) as a zero-length string, but for some reason it thinks that won't fit in the target field... Any ideas as to why it would behave this way? I can't say I know much about DBF files, or putting data into them for that matter.
SELECT normalfield, '' as blankstringfield, 0 as blanknumericfield
For some of the fields this works just fine, but for others it gives me the error "Field will not fit in record." If I use a blank field from the access database in place of '', it works just fine. i.e.
SELECT normalfield, blankDBfield as blankstringfield, 0 as blanknumericfield
I would think it would see '' (two single quotes) as a zero-length string, but for some reason it thinks that won't fit in the target field... Any ideas as to why it would behave this way? I can't say I know much about DBF files, or putting data into them for that matter.
Neither do I. Too bad.
I guess we'll have to wait for other member who might know more about dbf.
Or maybe you may try another method, why don't you try inserting using recordset.
Something like this :
Dim Rs,Rs1 as adodb.recordset
set rs = new adodb.recordset
rs.open " SELECT name, address, address2, now FROM [MyTable] JOIN [MyOtherTable] ON [MyTable].[id]=[MyOtherTab
rs1.open "select name, address, address2, now from [EXAMPLE]" '... blah... blah too.. connection, cursor and stuff
rs1.addnew
rs1.fields(0) = rs.fields(0)
rs1.fields(1) = rs.fields(1)
rs1.fields(2) = rs.fields(2)
rs.update
Maybe that onei'll wotk. Cause when recordset update a table, it create empty row first and then fill in the empty row with data. Just hope so.
I guess we'll have to wait for other member who might know more about dbf.
Or maybe you may try another method, why don't you try inserting using recordset.
Something like this :
Dim Rs,Rs1 as adodb.recordset
set rs = new adodb.recordset
rs.open " SELECT name, address, address2, now FROM [MyTable] JOIN [MyOtherTable] ON [MyTable].[id]=[MyOtherTab
rs1.open "select name, address, address2, now from [EXAMPLE]" '... blah... blah too.. connection, cursor and stuff
rs1.addnew
rs1.fields(0) = rs.fields(0)
rs1.fields(1) = rs.fields(1)
rs1.fields(2) = rs.fields(2)
rs.update
Maybe that onei'll wotk. Cause when recordset update a table, it create empty row first and then fill in the empty row with data. Just hope so.
ASKER
I suppose that's my next option. I'm kinda putting it off because there are so many fields. I mean, I like typing and all, but still.... my example was rather abbreviated. Although I suppose with as much time as I have spent on this I could have typed it out that way by now.
I'm wondering if I just hit some sort of upper limit on record size, because looking at the DBF files I'm creating, all the places I used '' as fieldname it assigns it a field length of 254. After so many empty fields like that, the record would get rather large in theoretical length. When I assign it a blank Access DB field with a set length of 1, it has no problem. Hmmmm.....
I'm wondering if I just hit some sort of upper limit on record size, because looking at the DBF files I'm creating, all the places I used '' as fieldname it assigns it a field length of 254. After so many empty fields like that, the record would get rather large in theoretical length. When I assign it a blank Access DB field with a set length of 1, it has no problem. Hmmmm.....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just to expand on jadedata recommendation. Use ADOX to create the tables and then insert records into them.
Leon
Leon
Frequently the "special" properties of fields that you like are not available in the ADO or ADOX object models.
But all object models can be copied and used as a new empty container.
But all object models can be copied and used as a new empty container.
ASKER
I think I would have to use a table of field specs to build the table on the fly, since the name of the table is created dynamically by the program. I'm not exactly sure how to do this, however, as databases are decidedly not my specialty. Anyone have any sample code I might use as a starting point?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think I can take it from here.
A big thank you to everyone that helped me with this problem!
A big thank you to everyone that helped me with this problem!
you're very welcome!
INTO [EXAMPLE]
FROM [MyTable]
JOIN [MyOtherTable]
ON [MyTable].[id]=[MyOtherTab
AND NOT [MyTable].[Imported] --what is this line for ? The field is not compared with any value.
Are your trying to insert some values from a database into another ?
I think it'll be better if you declare which fields you want to insert the value into.Like :
INTO [EXAMPLE] (name, address, address2, now)
I noticed that you are using Dbase 5. I don't know if dbase recognise this query. Why don't you convert the database to Access ? I guess Access is better than Dbase 5.