Form - Purchasing Input & Receipt Input

[Russ At Index]

Good Afternoon All,

As a newbie to Access, i have been tasked ( as an Excel wizard )
with producing a database which would house the following:
All information relating to the purchase order, vendor, sku,
description,value,ETA & Expected Qty.
This would be inputted by purchasing in the first instance.

As and when the goods arrive in the country , within the same form
with the above details visable the receiving team would enter :
Qty Rec'd,number of pallets,date of reciept.

Thus completing the PO for that delivery.

As i stated in te begining........... i'm am a newbie, any one
have any thoughts , ideas or even pitfalls to avoid ??

Any pointers would be appreciated.

Kind Regards

Russ

 

[MyBoo]

Research Normalization of tables FIRST and FOREMOST!

Create two databases - 1 Backend... to store your data and 1 Frontend... to store your forms, queries and reports. The Frontend db is what the users would work from. You link the Backend to the Frontend via File/Get External Data.

Once you create your backend db with all the tables defined (properly), click on Tools/Relationships and identify the relationships of all of your tables.

Ask questions if this is unfamiliar.

 

[Russ At Index]

Hi MyBoo,

Thanks for the prompt response, have taken your information
on board, and am currently searching this forum for guidelines
regarding split databases.

As i progress thru this project i will undoubtedly need further
education and assistance, Grover Park George has been purchased
so, with the literature and this forum i hope ( everything crossed )
to be able to complete the task. A tleast i have been given a favourable
time scale !

Thanks Agian , no doubt i will be in touch !!!!

Regards

Russ

 

[VicRauch]

Russ,

MyBoo is completely correct, but I would like to suggest that during the development stage, that you keep the database as a single database. It is VERY easy to split the database into two before you go into production, but while in development, having the tables in the same database as your queries, forms, and reports makes the job easier. Well, at least for me because I have never designed anything perfect the first time through. Therefore, I have to make minor adjustments to some of the data fields, add a few fields, and even a table every now and then as I develop the database. When making changes to anything within a table, if the database has already been split, you have to open the data database by itself in order to make changes to the tables. This is why it is easier to leave everything together before going into production. But, be sure to split the database into two before production. I just make a copy of the database, rename one to XXXXXXData, then remove all the querys, forms, reports, macros, and modules from that database. Then remove all the tables from the other database, and finally, link the XXXXXXData tables to the non-Data database. This may sound a little confusing, but it really is quite straight forward.
HTH,

 

[Russ At Index]

Hi Vic,

Thanks for the info , i am looking to start on my Access
journey sometime next week , i will apologise for my
"newbie" postings in advance !!!!

Thanks again , appreciate it.

Regards

Russ