DB critique?

arashii

Registered User.
Local time
Yesterday, 21:39
Joined
Feb 12, 2007
Messages
22
Hi, if this kind of request is pretty weird or uncommon, please just ignore me ~_~ . I’m a real newbie with Access, but was asked by a relative to try to create a very simple DB that will track her restaurant inventory. As such, I have come up with some sort of working (hopefully) DB, but I want to make sure that it’s not prone to crashing or suddenly losing or miscalculating the data, which would be disastrous.

Can you guys help critique my work? It’s very base, unprofessional, and the code is "forced" and all over the place. (But I think somehow it’s working, thanks to all the help I got from the people here ). I just need help in determining if there’s something critical I overlooked that might prove fatal to the database in the future.

The requirement is very simple. The only thing they really need to know is current amount of Items left in the inventory, and a sort of date log for the movement of Items. There is no need to keep track of any invoice/purchase data.

Thanks in advance for any brave soul willing to peek into my work. I’m really hesitant to show this to people here in the forums since everyone’s so good in Access and my work’s probably short of sloppy… but I do need to make sure I’m not going to cause havoc to my relative’s inventory tracking if she decides to use the DB and then it crashes lol.

Also, for any recommendations, please bear in mind my deplorable level of Access knowledge .

*crosses fingers*

BTW, the Item Catalog Management function is still not developed. The actual contents of the Item Catalog table is already the 'real' data and I didn't want to create test data that might ruin the working sheet .

http://download.yousendit.com/322DBA5463BB8969
*note: I think the file needs to be extracted out of the .zip folder first before it will work.
 

Users who are viewing this thread

Back
Top Bottom