Change 002

greenspun.com : LUSENET : SmartPart Development : One Thread

Status as of Tue 5th March 2002 at 10am

1.Until we get the source code for the ActiveX components, we have a blocker for change 002 : using the 'User maintenance' admin menu item to add or change a user to level 3 forces an account no (code) of 'Admin'. Once changed to 'Admin', reversion to any other level retains the 'Admin' account code. This is performed in the "Usermaintenance.clsUser" object. (There are no stored procs that it might use that set the value to 'Admin'). It does, however, allow level 4.

2.The SpareParts table is indeed used, but in UNION with the parts table for listing existing customer parts, and listing orderable parts. There is no asp SQL call that inserts/updates to the SpareParts table. Nor is there any use of the SP_INSERTPUMPSPARES stored proc in the asp code. There might be something on the ActiveX components.

-- Anonymous, March 05, 2002

Answers

Are you sure about the UNION clause? I have a gut feeling that parts are held in the Parts table only, and that the pump-parts relationship (I think in classic comp. sci. theory this is called 'explosion of parts') is held in the PumpSpares table and the pump-models parts relationship is held in the PumpModelSpares table. In both PumpSpares and PumpModelSpares the 'second' block of cols (PartCode, drawing, quantity, storescode) basically identifies the part (and how many are used...). If spares were held anywhere other than the Parts table we would expect another column, to show which table to look in to find the parts detail (probably...).

which is basically

-- Anonymous, March 07, 2002


Moderation questions? read the FAQ