Database

[kittykat8]

A while ago I mentioned doing a database, am going to do it now, But I lack imagination, what would have in you tables,as I know that they must not be clutted and repeat information. I have the skills to put one together but I don't what to put in the tables. Any ideas

marion

[piskieinboots]

when you say database - but you mean Access? If so, what is your end result - as this determins how you build the base, forgive if I prattle on with stuff you know

[Snadger]

when you say database - but you mean Access? If so, what is your end result - as this determins how you build the base, forgive if I prattle on with stuff you know

Once tried delving into the vagaries of Microsoft Access.........in the enamoured words of Neil from the Young Ones...."Heaaavy sh*t maaan"

[zazen999]

Piskie is right [as usual!].

You need to know your end user requirements [hark at her], before you design it. So, what do you want to know...possibly all the stuff on seed packets and more.

Try plotting out say 4 crops from planning to harvesting and storage, and seeing what info you would have kept to track it.

I used to write databases...now I stop at Excel and Pivot Tables.

[kittykat8]

I want to record evrything I do at the allotment, record all my seeds, which I suppose stock control, reorc what makes grow the best which will be results etc. I will use crystal reports to pull out the information. Any imput would be appreciated.

marion

[FionaH]

For basic stuff I find excel so much easier than access

[zazen999]

Now, if you look, someone on here has put together a database....I can't for the life of me remember who though. Try searching for database or spreadsheets....I knew I should have written it down!

It will come to me later probably - my memory isn't what it...what was I saying?

[piskieinboots]

..... my memory isn't what it...what was I saying?

who are you? do I know you?

Excel will most likely be more than sufficient for what you need - speak woth Hazel at the Hill, she has done such with Excel

I, personally, wouldn't use Access for what you want - excel is often more powerful than people think

[kittykat8]

But I want a database

[piskieinboots]

do you mind me asking why again - please tell me to sod off

What data do you want out of your DB?

[Alice]

Kittykat, you say you want a Database, but what you describe is actually more of a spreadsheet and the way to go with that is Excel. Hazel at the Hill did an excellent one. I don't know if it's possible for her to send it to you, but if you speak to her nicely I'm sure shell let you know.

[Alison]

I use excel for all this and it works a treat, always found that access was a bit inflexible and never seems to allow me to do what I want.

[piskieinboots]

I agree with all the above, Excel is excellent for garden recording - Access is a sladgehammer to crack a nut - but we all have different ways of how we do things ....so if you go down the Access route KK good luck

[Matt.]

In my opinion you should use excel as what you're after is a list or table. Each row represents a veg/seed type and various columns the fields you require - planned date planted, actual date planted, compost yes no, fertiliser yes no, bed location, price of seed, number of plants, supplier etc. Excel is perfect for this. If you then want to cross reference information per bed use vlookup commands or pivot tables to pull relevant data from your master table. This is still a database.

Access on the other hand is about building relationships between multiple tables. A great exmaple is the typical order management and stock inventory for a small business. They need to keep customer orders (names, addresses, items, previous items) in one area and business stock and wholesale separately. Access is a great way of linking the two to get a constant check on where you are or run pre defined reports. You could do this for your seeds but its a bit extreme (sledgehammer cracking a nut etc) unless you are a business like Sewer Rat.

edit - should have added access is also good for building forms. These are where you build front end applications for in-putting and manipulating your data. Typically when using an access database the user doesn't see the tables containing the data or any of the linking formulas. They just see a mini form or report where they perform a relevant task. E.g. Customer form would only contain fileds such as name & address. A blank order form would contain drop down menus of available products and a separate drop down to find the customer record. Essentially its a way of making something that is really quite complex behind the scenes very easy to use.

However if you want a project for practising access its a great start. Have a look at the examples that come with access to get you started. Good luck!

[bobleponge]

I have a copy of Hazel's excellent database that she very kindly sent me. If you want it Kittykat pm me and I will email it to you.