The design of K3 is a great god. It’s impossible to accept it. There are hundreds of fields in and out of the detailed list. Damn, there are many fields in one table. Many fields are understandable. Most of his grandma’s must not be empty, which is really rubbish. The best product in China, the front-end verification is empty, and the back-end consumes resources to verify. No wonder K3 is 100 times slower than the Mavericks, and it is also super slow to sub-databases and sub-tables!
Prompt "Cannot insert the value NULL into column FProperty"
SELECT * from ICInventory where FStockID not in (select FItemID from t_Stock), if there is a line item here, it means that the inventory ID is written incorrectly. This is a K3 design defect. In the in and out schedule, a field could be used to represent the inventory ID , Have to come up with 2 fields
I am professionally engaged in management software upgrades and in-depth transformations, including SAP, INFO, UFIDA, Jindie, etc. Welcome to discuss and make progress together!