Search options (Page 7 of 15)

So maybe they could all be the same value?
Seems odd to me...

I have not looked at osCommerce 3 yet and totally agree.

But the good news is that since I only rely on the database for information it may no be a hard change.
I'd just need to update the SQL entries, since after all it is still just a mysql database (I HOPE)

But, having just upgraded to 2.3.1, moving to 3.0 is not really on my priority list.

Tom
--
TEP 2.1, osc 2.2 core developer

Yeah maybe... I better upgrade to 2.3 first

Which report gives the item COST based on the manufacturing components?

Thanks to Janusz for pointing out my mistake.

I have submitted a new release for posting on the website.

I also added code to automatically detect if you are using the same DB for both.

It pretty much assumes that if the server and db name you give have osc tables in them
then you are using one DB, otherwise they are separate.

You still should use a unique mysql user if you are using different db's on the same server.

I look for the osc table 'order_status_history' actually I look for a table that contains that
string anywhere in the name kajsdfgajs_order_status_history_laksdaklsjd matches

I hope this helps

tom

@Jason - I will call it a Price List - If you edit a Price List it changes the price for all customers assigned to that Price List. You could have 1 price list for each customer, or have 3 different price lists and pick the price list based upon the customer's volume, negotiating skills, etc

@itronics: Sounds like Ed wants dynamic special pricing based on date, stock levels etc. FA can't do that, but on a Line by Line item you can change the price or set the discount.

@ed One way I could see to support this kind of pricing was if we were to expand the Sales type to include a Group of Price lists. For example the Sales type could retain the Price Factor to handle the default price (based on the Base Price List) and then an ordered list of price lists, if the item is not found in the First list, the second one is checked, etc If it is found you are done, if it was not found in any then use the Base Price * factor as it does now.

It might take a new table or a new field in an existing table but with a little bit of work it could be done and would be a great contribution to the project!

tom

Ok here I go with Backup in hand!

Thanks
ps. editing the database directly is NOT for the faint of heart! and *always* have a backup ready for when you DO mess up!

ckrosco - when you are done please send me your file and I will update and post the new file for all to use

Thanks!

Quantity is Quantity on hand
Demand is the Quantity requested by pending Sales Orders
Available is Quantity-Demand (possible negative)
On Order is the number on order via PO's

tom

I ran some tests on a test server.

I guess it is no surprise (to me now) that a Bank Payment to a Supplier is the same as a Purchasing -> Supplier Payment

Those payment should be made when I will be invoiced.

For my pay on demand I should use a Misc Payment or even a Quick entry.

So it now seems very logical that I will need to add a Dummy Invoice to allocate the payments to

tom