From: Paul Shapiro on
Did you also try a different computer? Or importing the dbf to Excel first?
The original dbf format was simply a fixed-length text file. If all else
fails, you could try importing it as fixed-length text. If I remember
correctly, the first character is a blank for a good row and a '*' for a
deleted row. The rest of the row is your data fields.

"Steve" <Steve(a)discussions.microsoft.com> wrote in message
news:03A561C8-C363-4FD9-AE61-05BF063283A9(a)microsoft.com...
> This is with any dbf file.
>
> "Jerry Whittle" wrote:
>
>> Any dbf file or just a particular file? If it's a particular file or
>> file(s),
>> I'd try to find another dbf file from a different system and try to
>> import it.
>> --
>> Jerry Whittle, Microsoft Access MVP
>> Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
>>
>>
>> "Steve" wrote:
>>
>> > I'm using Access 2003 and when I try to import a dbf file, Access
>> > crashes on
>> > me. I've already tried repairs and uninstall/reinstall of Office but
>> > that
>> > hasn't resolved the issue. I also am up to date on all service packs
>> > and
>> > updates. Not sure what to try next.


From: Jerry Whittle on
Can you link to the dbf file? (I think linking is possible).
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"Steve" wrote:

> This is with any dbf file.
>
> "Jerry Whittle" wrote:
>
> > Any dbf file or just a particular file? If it's a particular file or file(s),
> > I'd try to find another dbf file from a different system and try to import it.
> > --
> > Jerry Whittle, Microsoft Access MVP
> > Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
> >
> >
> > "Steve" wrote:
> >
> > > I'm using Access 2003 and when I try to import a dbf file, Access crashes on
> > > me. I've already tried repairs and uninstall/reinstall of Office but that
> > > hasn't resolved the issue. I also am up to date on all service packs and
> > > updates. Not sure what to try next.
From: Bob Quintal on
=?Utf-8?B?U3RldmU=?= <Steve(a)discussions.microsoft.com> wrote in
news:BC004898-55C3-4787-A2D2-19E9B415B247(a)microsoft.com:

> I'm using Access 2003 and when I try to import a dbf file, Access
> crashes on me. I've already tried repairs and uninstall/reinstall
> of Office but that hasn't resolved the issue. I also am up to
> date on all service packs and updates. Not sure what to try next.

Make sure the .dbf file name is eight characters or less.
ISTR that the import code balks at long file names on .dbf files.

--
Bob Quintal

PA is y I've altered my email address.
From: Paul Shapiro on
"Bob Quintal" <rquintal(a)sPAmpatico.ca> wrote in message
news:Xns9D40B78CB5909BQuintal(a)69.16.185.250...
> =?Utf-8?B?U3RldmU=?= <Steve(a)discussions.microsoft.com> wrote in
> news:BC004898-55C3-4787-A2D2-19E9B415B247(a)microsoft.com:
>
>> I'm using Access 2003 and when I try to import a dbf file, Access
>> crashes on me. I've already tried repairs and uninstall/reinstall
>> of Office but that hasn't resolved the issue. I also am up to
>> date on all service packs and updates. Not sure what to try next.
>
> Make sure the .dbf file name is eight characters or less.
> ISTR that the import code balks at long file names on .dbf files.
>
> --
> Bob Quintal
>
> PA is y I've altered my email address.

Good point! I'd forgotten that but I also seem to remember now that Bob
mentions it. You might also try a local folder with no spaces in the folder
names, and maybe no more than 8 characters for the folder names too. It's
been a while since trying to remember back to DOS days.

From: Steve on
Thank you for the responses. This happens with all dbf files and all mdb
files on my computer. It works fine on other computers though so the issue
is just on my computer. Yes, I can import other file formats like Excel
files. So I could bring the dbf into Excel then from Excel to Access,
however, I perform this operation quite often so I would like for it to work.
When Access crashes, it creates the .ldb file and I have to open Access
again and close it for the .ldb to disappear.
And yes, I am using a dbf file w/less than 8 characters in the name and
there are no spaces in the path name...which is local.

If by "linking" you mean opening vs importing the dbf in Access then that
doesn't work either...it also crashes Access.



"Paul Shapiro" wrote:

> "Bob Quintal" <rquintal(a)sPAmpatico.ca> wrote in message
> news:Xns9D40B78CB5909BQuintal(a)69.16.185.250...
> > =?Utf-8?B?U3RldmU=?= <Steve(a)discussions.microsoft.com> wrote in
> > news:BC004898-55C3-4787-A2D2-19E9B415B247(a)microsoft.com:
> >
> >> I'm using Access 2003 and when I try to import a dbf file, Access
> >> crashes on me. I've already tried repairs and uninstall/reinstall
> >> of Office but that hasn't resolved the issue. I also am up to
> >> date on all service packs and updates. Not sure what to try next.
> >
> > Make sure the .dbf file name is eight characters or less.
> > ISTR that the import code balks at long file names on .dbf files.
> >
> > --
> > Bob Quintal
> >
> > PA is y I've altered my email address.
>
> Good point! I'd forgotten that but I also seem to remember now that Bob
> mentions it. You might also try a local folder with no spaces in the folder
> names, and maybe no more than 8 characters for the folder names too. It's
> been a while since trying to remember back to DOS days.
>
> .
>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Filter using query
Next: Issues after 2K7 Conversion