DougP,
You are surprising me since you are one of the first guys in this forum. I will be clearer. If you go in supermarket which has meat, fruits etc, you can notice that they don’t have barcodes of course. But sales guy who gives you bananas seats near machine called label printing scale...
DougP,
No, the matter is much more complicated. I need to understand process of PLU (Product Look-Up) number generation. Other problem is how PLU file can be accessed by any barcode POS application.
fadMis
Bluelove,
Stock items have already barcodes but problem is for those that don't have them. Common case is with fruits which normally don't have barcode labels in them. Problem is solved with so called PLU (Product Look Up) numbers. Label printing scale prints label with barcode that can be...
I have created payroll database and I have table "Salaries" with EmployeeID (number), PayDate (date) and other fileds. I have form for calculating of salaries (with txtEmployeeID, txtPayDate) but before i store data in Salary table i need to check whether salary is already entered in table...
Hi John,
I have more complicated problem. Let assume that we have same table "testtable" but with ID and PayDate fields. Before i store data in table I need to check both fields at the same time, whether in table is already stored data for any ID and PayDate. It can be solved having ID and...
Hi
I just created POS application using MS Access. It works fine but I have problems understanding communication and printing label creation in any label printing scale such as CAS LP-1000 thermal label printing scale. I use EAN13 fonts so I would like to know how can I create labels for...
Great, thanks Tranman for your advices, I think I got your point. Now I agree with you having EmployeeID and PayDate as Primary Key. I would appreciate your code that prevents user to store double entry having error message because of duplicate key violation.
I think we are much closer now. Sorry for not being so clear previously. As I have given further explanation Salary table belongs to Many side, and that means that EmployeeID in Salary table is Foreign Key (which is redundant), normally because each Employee takes salary each month. Let me give...
Hi Tranman
It doesn't seem that the problem is solved. Salary table is in many side related with Employee table. There are 100 of Employees that take salary at the same date so PayDate can't be primary key. I tried with Dlookup and using FindFirst functions but I failed. In order to solve this...
I have two table in my access application, Employee and Salary table.
Employee Salary
--------- -------
EmployeeID EmployeeID
LastName PayDate
FirstName Salary
Location Allowance
JobTitle ---
--
I have form where I calculate salary and I store...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.