I agree and I thought about doing it this way, however since each day it would be appending hundreds of items. I figured I would run into a problem wiht too many rows before a month or two.
Check out below, showing an example of the way I was thinking it would work. The PN# column will usually have about 3000 items in it. Then each day the warehouse will cycle count a handful of the items, and I wanted to create a column to hold each days count serperatly. It is dealing with...
Skip..
Thanks for the heads up, I'm kinda new to the way things should be, and I am used to just trying to find ways to make them work.
In your case how would I make that line of code create a new column with a different name each time? Such as if I were to just type a "standardized" name...
I am simply trying to us a line of code
DoCmd.RunSQL "alter table tblphyinvrecords add column now() date"
To create a new column within this table with a label of the current system date.
That way each time someone inputs a daily cycle count it will record the counted number under the column...
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.