469,955 Members | 1,412 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,955 developers. It's quick & easy.

Imported DBF not pulling in all information

I have a process whereby I do some data processing outside of Access (in dbase IV format), then link the file back to Access to make some changes, then export the file to text. Recently, for no reason I can see, after I run the process on the dbase file and try to import, I get "Microsoft Access Index information (.inf) file already exists". No matter what option I choose, the linked file does not contain all the information appended to the dbase file during the external process. I can open the same dbase file in Excel and see that the updates to the data have been made, but in Access it's like they don't exist. So I thought, maybe I just need to import the data, rather than linking to the table. Same outcome. The fields that were updated show no data in Access, though the data is there. This is a process that has worked seamlessly for the last six months. What has changed, and how do I change it back?
Feb 7 '08 #1
1 1193
In order to help, I need to know alittle more information. If the data is being linked and you see it in the table then the problem has to be in the append query. First off,
1.) I would check to make sure there is no criteria that would eliminate these files from pulling in

2.) Check to see what the table you are linking in has the fields as (text, number,etc) then check to see what the table you are appending to has for these values. (In order to populate the data, they must be the same) Look at the table in design view for this description.

3.) Check the data that you are appending to ensure that there are no duplicates.

Let me know if this helps
Feb 13 '08 #2

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

5 posts views Thread by akelly_image | last post: by
2 posts views Thread by Joe Spears | last post: by
7 posts views Thread by colleen1980 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.