error in order tracking table

[fleetwood]

A customer has placed an exceptionally large order - 170 order lines.

On opening the order (and printing order), we get the message:

There was a problem with the database

Operation: Opening the [OrderTracking] table where nOrderSequenceNumber=20936

Data truncated.

Action: Contact Technical support

(Contacted tech support, who inform me they no longer support V5, and advised I post to the forum!).

I took a look at the order tracking table, and one of the fields - sProductDetails - was blank, whereas, all other records have an entry in. It was called something like 'order detail', and contained a number sequence (on the records other than this order).

Has anyone any idea on this one, or could at least tell me what the order tracking table is for.

Looks like I can process etc, albeit with the message popping up, but a little concerned about db corruption.

Thanks

[cdicken]

Hi Martin

The OrderTracking table produces that grid on the 'Shipping and Handling' tab of the order where you can choose which item goes in which package of the order. I imagine the 170 lines have exceeded some kind of field count for the order. If the order is complete, I suggest editing it and just remove any details from that grid for that order and it should stop the error message.

[fleetwood]

Hi Chris

Thanks for getting back - I was beginning to feel unloved

Basically, I appear to be able to do most things with the order (open, print etc), albeit that it reports an error every time I do anything.

I took a look at the shipping tab as suggested.
A package had not been created.
I am able to move products into a new package, but it then dosen't remember this when I exit shipping - no package shows up.

The relevant field in the table is the memo field sProductDetails, which is empty for this order. It appears to record all items ordered in one long memo entry.
A memo field in Access can be pretty large, so I'm guessing the problem with this order lies in somewhere in the processing of the data, which was just too large to handle, rather than any problem eventaully storing it in the memo field.

The bottom line is, can I fix it?
I did try making 2 smaller packages in the shipping tab, but like I said, the system won't recognise the packages (I assume because that memo field in that table is empty, when it should be populated with the order line detail).

I don't relish re-entering this entire order, so any further ideas I would be happy to give them a go.

[HowardW]

Hi Chris
I do not know whether this is related.
But one of our customers tried to put in an order for 487 items. The order was rejected.
We did it for her, by putting in the order for less than 99 items at a time.
Is there a limitation on the number of order lines per order?
If so it causes us a serious problem
Regards
Howard

[fleetwood]

That sounds like the same problem Howard.

How was the order 'rejected'?
Was the customer unable to checkout?
Did they receive a a message?
Or was the error only picked up when you opened the order?

Our order contains all the customer details, although I don't know if the customer was forced to checkout early - we haven't contacted them about it yet.
It does however, report a data truncated error, every time you open it, but then allows you to continue.
The only thing missing at the moment, is being unable to do anything with the shipping tab (not a major problem for us).

It does seem odd that the software should limit the number of items a customer can order though.

[cdicken]

I don't know if they are the same issue - one is to do with an order being placed at the website, and one is to do with processing an order on the desktop. I imagine the problem at the website is to do with the resources available on the server - ISPs only allow a certain amount of resources for Perl operations on the server (to stop malicious perl scripts from taking over) and an order as huge as 497 items could well have maxed it out.

With regards to the original problem of the order in the system, once you've processed the order, you can just delete the relevant record from the OrderTracking table. It doesn't do any harm.

[fleetwood]

With regards to the original problem of the order in the system, once you've processed the order, you can just delete the relevant record from the OrderTracking table. It doesn't do any harm.

Thanks Chris.

It doesn't do any harm.

Thats the bit I needed to hear