Hello, Frank,
I am very sorry to hear that, and yes, it is very frustrating. I'm
not a "guru" for .qif importing or anything else for that matter, but
I did some experimentation with .QIF files some weeks ago. But just
off the top of my head, I would suggest:
-Are you sure your version of Quick
Frank,
I just tried the QIF importer on a tiny file that I had laying around. For
this test I was using release 2.6.15 in Windows.
I found that the QIF importer is somewhat tedious to use initially until it
has some history in it's memory from previous imports. After several steps
of finding th
Frank,
Sorry to hear about that misfortune.
Theoretically you you can use file > replay log and that may get you close
to where it was before it crashed, but in your case that may not be your
best choice.
I suggest writing up your experiences so far to learning about some of the
mistakes that Gn
Just finished 6 hours correcting all the data i imported and before I could
save it, the program crashed. All I have is the unchanged imported data
fileWhen it crashed, the file was lost but there is a log
file..what it is I don't know. Guess I have to start all over?
Frankie
On 7 October 2017 at 9:28, Steve said:
> Fred Bone wrote
> > Perhaps it's objecting to the MS-DOS-style line endings, that Notepad
> > will have helpfully put there for you?
> >
> > If you put a file there with one line containing just a semicolon and it
> > still won't run, then that's the probl
