PDA

View Full Version : Need to save after importing


Lisa_p
03-13-2008, 03:33 PM
It seems that sometimes when you import list info, the first time you then open a record in Peachtree, you get the message that you've modified the record, do you want to save, even if you haven't done anything but look at it.

It seems that once you save it, it doesn't bug you again, but it's very annoying when you've imported thousands of records.

Any way to prevent that?

rick Prindivill
03-13-2008, 06:32 PM
Please identify the type of list being imported and the version of Peachtree being updated and anything more that you may feel to be relevant. I do not recall having experienced this problem as you have listed it and I would like to try and replicate it.

Lisa_p
03-13-2008, 07:22 PM
I know I've run into it before, but specifically right now, it's Quantum 2008 and the inventory list. I'm importing the following fields:

ID
Desc
Desc for Sales
Weight
Item Class
Price
UOM
Item Type
Taxable
Custom field 1
Custom field 2
Last cost
GL Sales
GL Inventory
GL COGS

It's definitely annoying! Let me know if you can duplicate it. Thanks!

LauraG
03-14-2008, 06:55 AM
I ran into that problem when importing a budget into the Chart of Accounts. I had to go into each G/L account and manually save it. Very annoying.

I wonder if changing the posting method to Batch prior to the import and then manually post all transactions would eliminate the problem.

TheWolf
03-14-2008, 07:37 AM
Batch posting only posts transactions. I have run into the problem before, and it is often a field that is not imported but there is default information set for it. I have found that rather than spend a lot of time finding the field, I run DV and it corrects it. There have been rare occasions when DV did not correct it, and we had to do a manual save. I did not have the time to run down which field was causing it every time, but the times I did, it was always some default information fields (example: terms for customers).

Lisa_p
03-14-2008, 10:15 AM
DANG! DV didn't take care of it - I thought I was going to get to be the hero. Oh well.

Makes sense that a default field is the culprit, since then yes, the record has changed from what was imported.

Thanks Tom.