Database for daily entry of records datewise.

[Goldenbird]

I want to prepare a database which may look like this. Each day I have to enter data like this datewise. Suppose this is for 13/06/2010, then again on 14/06/2010 same type of data. How can I make a database in Access 2007 datewise :-

Date 13/06/2010

Area purchased sold left


SKN 50 20 30
PNQ 20 05 15
RMS 64 04 60
SLK 85 05 80
GZB 66 06 60

The main problem is how to make above database based on each day. Please guide.

[Access_Blaster]

Add and customize date and time formats:

http://office.microsoft.com/en-us/ac...78108.aspx#BM2


Richard

[Goldenbird]

Thanks Access Blaster. I know how to customize date and time formats. I just want to know how can I incorporate date for my database. If I incorporate a Date field then I have to type date for all records. I just want to know how can I incorporate date field in my database for each day.

[kimmer]

You need a date field. You can make it default to NOW().
Alternatively, a quick way to enter the current date is Ctrl+;

What is the field "left" for? It looks like it is the result of a calculation.

[Goldenbird]

Thanks kimmer Sir. If I make a date field before Area, then I have to put Now() or present date in all records which is repetitive. Then again on another date I have to entry another figures , but the area records will remain same only the date and purchased, sold, left records will change. Please tell me can I attach a sample file or how to insert the access form in the post.

[kimmer]

Yes, you need a date in each record, repetitive or not. This is fine; records are cheap. You will add a record each time there is a transaction. In addition to the fields you have (but as I said, I think "Left" is redundant), I would also have an autonumbr primary key if I were you.

You can click the Go Advanced button to find the tool for uploading a file.

[Goldenbird]

Thanks for your reply. Attached is the image and file also. Please go through and tell me how to simplify this Database. Please see that the records of the Projects are repetitive and is required to be entered each day. In the same way dates are also to be entered for each and every project records. I want a proper idea as to how can I make a database so as not to repeat dates and Projects records each day repititively.

[Goldenbird]

Kind attention. Administrators where you all are. I am very much hopeful from this forum. Else if no solution, then I will move to another site/forum. So its a appeal once again to kindly have a look at the files/image and suggest me simple ways to maintain database.

[JohnBoy]

Hi I had a look at what your doing and would agree with Kimmer on the date field, if you set the default value in your date field properties in the table to Now() that will take care of automating that bit, or am I missing something

JB

[Goldenbird]

Thanks Johnboy for your suggestion. I too agree with Kimmer. But suppose I have to put another date other than Now(). Another question what I asked was how could I simplify my work so that I have not to type the 10 Projects daily which I think you would have seen in the attached file. The 10 projects are repeated daily. Suggest me a way where the 10 projects which are repitetive automatically appear for next 10 records.

[Access_Blaster]

Wouldn't life be simpler if in your main form, you had a date field and a project combo box? And in your sub form has related records? Since all your fields seem to be DAILY requirement, why would you have mixed dates in your sub form? Sorry but I really don't get this.

[JohnBoy]

This would be my answer to, however as a side thought, are you asking for a way to load the Projects on open along with their Coal Daily as these seem to be constants each day while the other seem to vary.. if so you could just build a table containing the project names and the fixed Daily Coal field and run an append query on open or from a cmd button to insert them and then manually update the other fields, but I would go for the other solution using a combo box etc, you are also using Date as a field name which is an access reserved word and may cause some problems for you (Or not as the case may be) but just be carefull using reserved words as field names

[Goldenbird]

I really thank very much to JohnBoy & specially Access Blaster for their valuable support and sparing time for me. As per your suggestions, I have come to a conclusion. I was not thinking of making a ProjectID or Daily ID which was a mistake. AccessBlaster has attached a file and I will go through that way as he has suggested. I will change the name of Date Field as suggested. Hope for your future support too.

[Access_Blaster]

When you start with a more normalized tables and relationships, you don't have to constantly come up with creative solutions to get your data out. Also a side benefit of normalize database is you can get quick answers to your questions. My sample would be a very simple starting point it could be very complex if needed.


Regards,


Richard