Help! Can't Add Quantity Dependent Pricing

[jarroyo]

I Cannot coax my business catalog V. 5.1.6.1 to allow me to add quantity dependent pricing. Everytime I try to add another line into the pricing under ANY price schedule, it errors out and exits the program. I have tried taking out the price schedules completely, I tried to import pricing with quantity dependent pricing, but have not yet been successful. The following error was generated:

AppName: catalog.exe AppVer: 5.1.6.1 ModName: catalog.exe
ModVer: 5.1.6.1 Offset: 001d3d15

Also, by default in my pricing, MIN is greyed out and there is no MAX setting anymore.

I currently have price schedules, also a patch for Authorize.net. Any ideas? The next idea is to try to go backward in Versions, try to correct the problem, then go back up to the current V 5.1.6.1

I am attaching the complete error text file to this message:

[cdicken]

To be honest, it sounds like your database has somehow become corrupted. The 'Prices' tab is displaying OK (v5 has no 'Max' column) but something is definitely going wrong.

You are doing all the sensible things I would have suggested. I would also try going to 'Housekeeping | Compact Databases' and see if that helps things.

The next step is probably contacting our support dept via email here (http://www.actinic.co.uk/support/register.htm) and they will take a look at your database and try and correct the problem.

[jarroyo]

Well, tried that and still have the MIN greyed out and, when clicking on that little + sign in the prices, it still craters and does the error report as it crashes.

What do you want me to send you?:confused:

[jarroyo]

to 5.1.4 instead of 5.1.6? I have to keep the Authorize.net update to SIM of course to keep payment options, will that be affected? It occurred to me that I did not have that problem before doing that. Also, I am actually on a different machine from when I first had this problem, I moved machines hoping it would work on another and imported a snapshot from the other machine. Apparently, the snapshot has carried the problem. Can I export a hierarchtical export into excel, wipe away the site completely, then import the raw data back in.

Ideas appreciated

[cdicken]

Don't send me anything. Just click the link I sent you to register an email support query.

[jarroyo]

I did the compact database. I even went into Access and manually compacted each table, no positive result. I uninstalled and reinstalled but did not get it to work that way. However, on the new Site 1, it does work but, of course, I do not relish the idea of manually inputting over 1000 products! You did not include a link but I went to the actinic site and entered an email support request.

[jarroyo]

It seems that the snapshot itself is corrupted somehow. I have tried to use the Compact Databases but it does not work, whenever I try to click the Plus sign to add a price schedule (so I can add a quantity-dependent price), the Actinic program crashes. I have installed Actinic on 3 different machines now and have the same problem on all three machines (XP Professional, and Windows 2000 Professional). I am at WITS End! Please, does ANYONE have an idea of why?

I have tried to use Access to clean up the tables individually, it found nothing. I have tried to use Export and use a csv file to import a clean database. Still no luck.

[jarroyo]

I installed V6 to see if the problem transferred to the newest rev. It actually works on V6 but, of course, I have not purchased this rev yet and don't have the budget to go there yet! (Heck, at the moment, I still have 4 V5 Catalogs in inventory which do not have any hope of seeing a customer! I would GLADLY trade those for ONE V6!!!!)

[jarroyo]

In Actinic Business 5? I am beginning to wonder if maybe I simply maxed out the program? There has GOT to be a reasonable explanation for this crashing on different computers and operating systems (I just CANNOT be that unlucky!)

[jarroyo]

Actinic US support sent me an email with the solution. This is SO SIMPLE it is almost pathetic!

the fix:
I've reproduced the error. This is a bug which has been fixed in version 6.

The workaround is to rename the main price schedule (currently 'Price') back to 'Retail'.