Re: to normailise or not?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The data is in a spread*** at the moment. One *** per course (many
classes per ***).

If fact I was thinking that once I had it in a database instead I would link
a spread*** to it so that staff could see the data and make ad hoc
calculations using excel

Yes I did play around with formatting columns in access and although it can
be done it is a bit of a pain. Easier in Excel.

As for the link to word I knocked up a database to do a mailmerge from my
spread*** via access only last week! Doing the complex queries I needed
was easir in access than doing filters in excel.

Good food for thought Thank you. I'd rather normalise the data but it was
the ease of entry bit that was worrying me. What you all suggest seems a
good idea and fun to code!
Howard



"Tim Ferguson" <FergusonTG@xxxxxxxxxxxx> wrote in message
news:Xns96E89ED5AC08Bgarbleme4455656@xxxxxxxxxxxxxxxx
> "Howard" <nospam@xxxxxxxxxxxxxxxxx> wrote in
> news:lMudncxS4NHNFtjenZ2dnUVZ8qidnZ2d@xxxxxxxxx:
>
>>
>> In Excel its easy, one row per student, one column for name, other
>> columns for marks - How can I duplicate this idea in Access without
>> having to see only one student at a time with a subform of all their
>> assignments?
>>
>>
>
> I am with Vincent on this one: why not do the whole lot in Excel? With a
> decent normalised design, say
>
> ReceivedMarks (
> StudentID long_integer FK references Students,
> AssignmentCode NChar(5) FK references Assignments,
> ScoredValue integer NOT NULL
>
> primarykey (StudentID, AssignmentCode)
> )
>
>
> then you can use code in the Worksheet_Open event to read in the Students
> and Assignments tables to fill in the column and row headings. Then read
> in the ReceivedMarks table and fill in the appropriate cells.
>
> To save the values, you could either catch the Worksheet_Change event and
> write individual values back to the table, or wait for the user to close
> down and catch the Worksheet_Close event. In the latter case, you'd want
> a menu or command button to call an explicit Save. Then the code would
> need to go through all the cells, and either DELETE a record if the cell
> was empty, or INSERT or UPDATE it if it wasn't.
>
> Not too hard to do. Remember that you can then use all Excel's layout
> features like decent printing, data validation, sorting, immediate
> calculation, and so on. The VBA and data access code (ADO or DAO
> according to choice) in Excel is exactly the same as you would use in
> Access.
>
> Hope that helps
>
>
> Tim F
>


.

Quantcast