Here is my version of Sage 50 Pro

Oliver

I don't have 2014.0 installed but I just tested 2014.2 and it imported your file properly with the company file setup you have.  It works on a file in 2015 and 2021.1 as well.

One thing that comes to mind is something that occurred to another client of mine running a high end ERP system recently.  The short story is that two digit years are converted to 19xx instead of 20xx.

There is a setting in Windows control panel Regional Settings that controls the range of dates for two digit years.  Mine is set from 1930 to 2029, so when 20 is used, 20 is appended to the beginning because it is under 29.

Try using a four-digit year in the import file and if that doesn't work, then try changing your Regional Settings if it tops out at 2019.  I may have edited mine because I have had a client hit this issue before and for me to do the programming required for them, I had to change my settings.

Make sure there is no blank lines the beginning, etc.  And if that doesn't work, attach your exact sample file and I will download it and test it exactly as you have it set up.

Interesting!

Interesting!

On the surface, yes i can see it is interesting but I was neck deep in a Pervasive database and found the programmers of that particular system thought it was a good idea to store every single date in every single table as a 6-digit text string.  This includes in our case the start date of every employee.

Each employee that started in 2020 had been with the company over 100 years because, for reporting, the Views were programmed to take any date with the last two characters 19 and under and add 20 but if the last two characters were 20 or more then they added 19 to the beginning of the year.  Windows will do the same thing in programs like Excel but I believe the defaults have been increased to 2029 now.

Hi Richard,

Really appreciate your suggestions. I made the changes in Windows 10.  See below Reboot and import again.  It still said the transaction date must be between the fiscal end date and earliest transaction date.  :-(  I also try changing the short date format as mm/dd/yy and mm/dd/yyyy

I also change the date to 12-27-2020 in the import file.  Still the same. :(

May be I need to shop for new version ?

I really doubt there is a bug in the system that doesn't allow 2014.0 to import but 2014.2 does however, before you upgrade to a new version, you might install the update to 2014.

However, before you even do this

Richard S. Ridings said:

What happens when you copy the entry from your message above into Notepad and save it, then import it?  This is what I did.

If this works, then instead of copying from Excel to Notepad, in Excel, Save As and use a *.prn file format.  Then try to import it.

Hi Ricard,

Thanks for the other suggestions.  That is what I did also.  I type the info directly in Notepard to create the import txt file.  I tried the .prn format as well.  Fail either.  Hmmm.. I have another laptop that I can try to install Sage and try to setup a new dummy company to import.   Again.. Appreciate all your suggestion. 

Thanks

Oliver.