Description of the database structure for uploading Food and Beverage wireless ordering module to PDA

Database file data structure: menumenuid recipe No. 0000 ~ 9999, of which 0000 is the spellcode pinyin code dishname which is not found on the Self-ordered menu. The name of the dish is unitid. The unit price is the unit price. iscurrentprice: whether the seasonal price is kitchenerid.CodeSortid category No. cost price issue can be clicked dashsortsortid category No. 001 ~ 999sort category content tabletableid platform No. 0001 ~ 9999tablename station No. Name memomemoid remarks No. 001 ~ 999memoname remarks uploaded data format: Platform number, 0x1b, serial number, 0x1b, Recipe number, 0x1b, quantity, 0x1b, remarks, 0x1b, food return tag, 0x1b, 0x0d 2nd: Platform number, 0x1b, serial number, 0x1b, Recipe number, 0x1b, quantity, 0x1b, remarks, 0x1b, food return mark, 0x1b, 0x0d 3rd: Platform number, 0x1b, sequence Number, 0x1b, Recipe number, 0x1b, quantity, 0x1b, remarks, 0x1b, backfood mark, 0x1b, 0x0d, 4th: Platform number, 0x1b, sequence number, 0x1b, Recipe number, 0x1b, quantity, 0x1b, remarks, 0x1b, backfood mark, 0x1b, 0x0d ...... End sign: station number, 0x1b, 0x0c, 0x0c, 0x0c, 0x1b, 0x0d Note: 1. "route X:" indicates that the information is not the data content. 2. "End flag:" indicates that the information is not the data content. 3. the preceding comma is a delimiter, not a data content. 4. "0x1b" and "0x0d" are ASCII 5. the number of dishes uploaded each time is not fixed. The ending mark is the end.