Solved

Paradox table inport error

Posted on 2004-04-12
18
561 Views
Last Modified: 2012-05-04
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
0
Comment
Question by:cpopham
  • 9
  • 8
18 Comments
 
LVL 32

Expert Comment

by:jadedata
ID: 10804791
Greetings cpopham!

You have to explain the steps in the import operation...
How are you getting the data into Access from Paradox?

regards
jack
0
 
LVL 32

Expert Comment

by:jadedata
ID: 10804806
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.
0
 

Author Comment

by:cpopham
ID: 10804843
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"
0
 
LVL 32

Expert Comment

by:jadedata
ID: 10804863
let me see the sql for query that actually is responsible for the error.
0
 

Author Comment

by:cpopham
ID: 10804885
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
0
 
LVL 32

Expert Comment

by:jadedata
ID: 10804951
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??
0
 

Author Comment

by:cpopham
ID: 10805235
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
0
 
LVL 32

Accepted Solution

by:
jadedata earned 105 total points
ID: 10805267
There is some kind of error in that Paradox input table.
0
 

Author Comment

by:cpopham
ID: 10805273
That was what I was thinking, but I can not seem to find it anywhere...
0
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

 
LVL 32

Expert Comment

by:jadedata
ID: 10805285
Will the table link (attach) as a table correctly?  
Does the file originator see anything suspicious looking at the file in Paradox?
0
 

Author Comment

by:cpopham
ID: 10805309
No it will not link correctly.  No they say nothing is wrong.

0
 
LVL 32

Expert Comment

by:jadedata
ID: 10805319
You need to make absolutely sure you have the correct and most current data drivers for Borland's Paradox product...
0
 

Author Comment

by:cpopham
ID: 10805341
Does office Service Pack 3 do anything that might cause this?

0
 
LVL 32

Expert Comment

by:jadedata
ID: 10805375
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.
0
 

Author Comment

by:cpopham
ID: 10805387
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
0
 

Author Comment

by:cpopham
ID: 10806110
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
0
 
LVL 32

Expert Comment

by:jadedata
ID: 10806142
There was some teeny weeny bit out of place enough to have Access reject it.
0
 

Expert Comment

by:JuanQuichote
ID: 23325829
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!
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Today's users almost expect this to happen in all search boxes. After all, if their favourite search engine juggles with tens of thousand keywords while they type, and suggests matching phrases on the fly, why shouldn't they expect the same from you…
Introduction When developing Access applications, often we need to know whether an object exists.  This article presents a quick and reliable routine to determine if an object exists without that object being opened. If you wanted to inspect/ite…
In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

24 Experts available now in Live!

Get 1:1 Help Now