Software programming, doubts about order numbers

This is a question that complicates you.

A similar problem can be solved by using formatted strings.

int a = 1;

string b = "%06d", a);

So the string b is 000001.

among others"%06d", 0 represents 0, 6 represents the total length, and a is the following number.

Be sure to use my answers, deal with it that way, and use the rest to make the rest of the project team laugh at...

It's best to use triggers when committing to the database. Or:

theordnum="00000"+ordno;

theordnum=

It's simple. Hehe.

I'm also a beginner, and I think it's okay to think about the landlord's problem:

There is nothing wrong with int type variables incrementing as numbers, but converting them to strings is a bit more complicated, you can use divisibility and these methods to determine the number of digits of a number, and then decide how many zeros to add, there is no need to convert to a string and calculate the length.

To create an order schedule, record the order number, product number, quantity, and other information, and then you can associate the order table with the order number to form a master-slave table relationship.

The order table (including the order number, order date, order person, etc.), and its primary key is the order number.

The primary key of the product table (including the product number, product name, model specification, etc.) is the product number.

The order list (including the order number, product number, order quantity, remarks, etc.), whose primary key is order number + product number, has the following syntax: create product details (order number char(10), product number char(10), .primary ke (order number, product number).

Access is a relational database management system published by Microsoft. It combines the features of the Microsoft Jet Database Engine with a graphical user interface, and is a member of Microsoft Office that provides access to data from Access Jet, Microsoft SQL Server, Oracle, or any ODBC-compatible database.

Software developers and data architects can use Microsoft Access to develop application software, which "power users" can use to build software applications. Like other office applications, Access supports the Visual Basic macro language, which is an object-oriented programming language that can reference a variety of objects, including DAOs.

ActiveX data objects as well as many other ActiveX components. Visual objects are used to display tables and reports, and their methods and properties are in the context of VBA programming, and VBA modules can declare and invoke Windows operating system functions.

It is best that the order number can be high concurrency and generate unique, otherwise it will be embarrassing if there are duplicates.

Too short is prone to repetition.

Suggestion: Time + User ID + Several random numbers.

Simple time + id + random number.

Preferably three tables:

1.The order table (including the order number, order date, order person, etc.), its primary key is order number 2The primary key of the product table (including product number, product name, model specification, etc.) is product number 3

The order schedule (including the order number, product number, order quantity, notes, etc.) is a composite primary key of order number + product number.

The syntax is as follows: create a product schedule (order number char(10), product number char(10), .primary ke (order number, product number).

If it is a program, you can write it to the db and look it up again according to the order number just written, and it will be very fast.

What's so hard to fix here? Your own database is well defined, for example, the value of the status store is: 1-save, 2-submit, 3-to be shipped, 4-shipped, 5-closed, etc., and the order status changes according to the order number, modify the value of the status field of this order according to the order number to the corresponding status value.

Here order and product is a typical many-to-many relationship, so try not to put it in a table to store ah, you can create another order and product relationship table to store these records, otherwise you will never be able to write what your pro id is, unless you specify a delimiter to connect all pro ids to form a varcher, but this will lead to trouble in program processing, It's not as concise as a separate relationship table.

I don't really understand the meaning of the expression, can you describe it in detail.

According to the screenshot, what do you mean by the status of the order?

We can discuss the specifics.

It is advisable to find an outsourcing company.