(10-28-2015, 02:44 AM)falkoner Wrote: Hi Bill, moving to a 32 character stock code is easy, just a case of making sure you get all the tables that reference that field, and changing the Stocks.php validation checks. For very large inventories (I have customers with > 1m part codes) it would have some performance impact but probably not significant. I would be interested to know why you need 32?
As far as I am aware there is no problem with PHP versions. I did the 5.3 changes myself a while back and since then there hasn't been great changes. I am currently running PHP 5.5.9-1ubuntu4.13 without an issues. Is your point that we keep backwards compatibility with older PHP versions?
As for the "illegal characters" that is a bigger issue. Some can just be got rid of as the don't make any difference. With the others it is possible but requires quite a lot of work.
Tim
Thanks Tim,
The 32 could be 50. I was thinking of a specific supplier that actually uses 32.
Myself I think all parts number should be assigned sequentially when they get past 12.
The PHP version was a concern only from the point of view that the installation instructions seems to indicate the recommendation is to stay at the earlier version (PHP 5.2.x?) We only have a couple installs and so we are not so concerned about backward as much as being able to take advantage of newer release capabilities. (Our Group is focused right now on Point Of Sale). We were also concerned about being able to obtain earlier releases of PHP and what we do if they became unavailable.
Two particular characters are . and (space). O-ring distributors and mfg's use . as part of their part numbers.
The guys that have large part numbers will use (space) to separate segments in their part numbers.
Most US fabricators will use ' and " to indicate ft or in (USA not metric) and . and (space). They also tend to have large part numbers due to dimensional indicators within their part numbers.
Do you know the ones that can be gotten rid of?
Thanks again,
Bill