cpopham
asked on
Paradox table inport error
I have a small Access program that runs monthly. It imports two Paradox tables and then runs a query against them. Well nothing ahs changed with my job and nothing has changed with the Paradox tables, but now I can not get one of the tables to import. The other table appears to import fine. The error that I am getting is this:
Error Code 3219:
Invalid operation.
When I look this up it says soemthing about duplicate fields, but the tables ahve not changed and THERE ARE NO DUPLICATE fields. Has anyone got any ideas as to what happened and hpw I can fix this?
Thansk, Chester
Error Code 3219:
Invalid operation.
When I look this up it says soemthing about duplicate fields, but the tables ahve not changed and THERE ARE NO DUPLICATE fields. Has anyone got any ideas as to what happened and hpw I can fix this?
Thansk, Chester
never mind....
It imports two Paradox tables and then runs a query against them.
Have you consider just linking these tables instead of importing them?
Something changed somewhere in the operation or in the structures. Or else nothing new would be occurring.
Check with the folks who supply the paradox data for ANY changes they have made to their systems that could even remotely have an impact on the data. (new/changed indexes ALSO)
There could also be some defect in the data stream that is causing this. Request a "fresh" copy of the data.
Check for/correct for corruption on your side as well.
It imports two Paradox tables and then runs a query against them.
Have you consider just linking these tables instead of importing them?
Something changed somewhere in the operation or in the structures. Or else nothing new would be occurring.
Check with the folks who supply the paradox data for ANY changes they have made to their systems that could even remotely have an impact on the data. (new/changed indexes ALSO)
There could also be some defect in the data stream that is causing this. Request a "fresh" copy of the data.
Check for/correct for corruption on your side as well.
ASKER
They say they have changed nothing and I have even compared the newest tables to soem old ones we had as backup and nothing changed. I tried linkling the tables and instead of the column headings, it gives me column0 column1, column2, etc.
This is the bit of code that imports the tables:
DoCmd.TransferDatabase acImport, "Paradox 7.X", "P:\Fleet", acTable, "Fleet.DB", "Fleet", False
' Import LeaseRates DataBase
DoCmd.TransferDatabase acImport, "Paradox 7.X", "P:\Fleet", acTable, "lert.DB", "LeaseRates", False
' Open CombineData Query to Create New Table
DoCmd.OpenQuery "QryCombineData", acViewNormal, acReadOnly
' Close CombineData Query
DoCmd.Close acQuery, "QryCombineData"
This is the bit of code that imports the tables:
DoCmd.TransferDatabase acImport, "Paradox 7.X", "P:\Fleet", acTable, "Fleet.DB", "Fleet", False
' Import LeaseRates DataBase
DoCmd.TransferDatabase acImport, "Paradox 7.X", "P:\Fleet", acTable, "lert.DB", "LeaseRates", False
' Open CombineData Query to Create New Table
DoCmd.OpenQuery "QryCombineData", acViewNormal, acReadOnly
' Close CombineData Query
DoCmd.Close acQuery, "QryCombineData"
let me see the sql for query that actually is responsible for the error.
ASKER
Jack, it erros out before it ever gets to the SQL. It errors on the first acImport statement. I have been able to import the second one manually, but still cannot get the first one to import correctly. I did go into Paradox the first day and save the table as an excel spreadsheet and then import that into Access and everything was fine with that.
Chester
Chester
how (exactly) do you mean you saved a Paradox table AS a excel spreadsheet??
I've never been a real fan of TransferDatabase.... too much room for error and insufficient control over the general operation.
Can you conduct the same (as the one that errors out) import manually??
I've never been a real fan of TransferDatabase.... too much room for error and insufficient control over the general operation.
Can you conduct the same (as the one that errors out) import manually??
ASKER
No, I get the same rror when I try to import manually. I went into Paradox and did Table Save As and saved it as an Excel Document...
Chester
Chester
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That was what I was thinking, but I can not seem to find it anywhere...
Will the table link (attach) as a table correctly?
Does the file originator see anything suspicious looking at the file in Paradox?
Does the file originator see anything suspicious looking at the file in Paradox?
ASKER
No it will not link correctly. No they say nothing is wrong.
You need to make absolutely sure you have the correct and most current data drivers for Borland's Paradox product...
ASKER
Does office Service Pack 3 do anything that might cause this?
as in "you just deployed Service Pack 3" or "you do not yet have SP3 installed"?
frankly I don't' think I know enough to say for sure.
It could have been a butterfly farted in China that caused this.
frankly I don't' think I know enough to say for sure.
It could have been a butterfly farted in China that caused this.
ASKER
I just installed SP 3 and was wondering what effect it would have. I am going to try installing PAradox on my machine, importing the users tables into a new Paradox table and renaming it under the old name to see what that will do. I have the most recent Borland drivers installed also. I told them just to go ahead and convert to Access, but they do not want to do that yet!
Chester
Chester
ASKER
After installing Paradox and then importing the afflicted Paradox table into Paradox and then renaming it to the old one the import now works fine!
Chester
Chester
There was some teeny weeny bit out of place enough to have Access reject it.
I had a very similar problem with some Paradox tables which caused an error when I tried to import them into Access. By trial and error, I found that the presence of certain Paradox Index files with the same name in the same directory were responsible (e.g. one with the extension .PX). After removing those, the import went smoothly (and the indexes can be re-created in Access). Renaming the table of course has the same effect. No re-installation of any program or importing into Paradox is necessary!
You have to explain the steps in the import operation...
How are you getting the data into Access from Paradox?
regards
jack