The first question we have to ask when starting a data load is what type of data load you are doing. Here are some of the types of data loads:

• Price update: You are updating your prices from a supplier price list. If you are trying to adjust your prices by a percentage or some simular method, please look at the Price Adjustments feature within System Five (Look up the index: Price Adjustments in our help file).
• Initial Data Load: You are adding new inventory and trying to get the information you have into the correct spot in System Five
• Inventory information update: You are updating existing, and maybe adding some missing items to your inventory. There may be fields that you are updating that do not exist in the auxilliary database.
• Advanced data loading procedures and getting existing data ready for a data load: You may be required to reformat, and find ways to deal with features that work differently. Someone with a very thorough knowledge of System Five data requirements, and data manipulation is often required.
• RPSC Import: You are importing information exported from RPSC data using the RPSC Export Wizard

In order to remove a set of parts there are a few ways to approach the problem.

• Use the toolbox routine to permanently remove all items with a specified supplier ex: delete me
• Use the data load functionality within system five to load a Y into the marked for deletion flag.

If you are trying to permanently remove items please note that System Five will Remove where possible, and mark for deletion the rest. I don't believe the toolbox routine looks at Marked for Deletion items.

If you are looking to import invoices, the big question is WHY?.

• Customer balances come across in your startup procedure so unless you need more specific dating or detail information you don't really need to import invoices.

• Invoice history does not come over well, and there are many challenges when trying to create this history. As a result of the challenges that come up, we do not support importing this history.
• Please use your old system as your history.

• Have someone experienced with the clients data look it over for accuracy and completeness. The technician doing the data load should examine first to catch the more obvious mistakes, and then the client themselves need to take a thorough look doing any necessary testing.
• Repair and compact the database after large data operations like restarts. This may restore the database to its thinner state.

Field Usage

• customer_load_hangs_while_loading_preview