| re: Data Correlation
See notes per point below
"Justin Hoffman" <j@b.com> wrote in message
news:d07uoe$mpr$1@hercules.btinternet.com...
Before you look at how to format the output, have you decided how you are[color=blue]
> going to structure and store the data? Having studied Oracle, you must
> have a reasonable idea of relational database structures and may have
> already made some decisions. Perhaps you have started with something
> like:
> tblDrawing: DwgNumber, DwgName, etc
> tblRevision: DwgNumber, RevLetter, RevDate, etc[/color]
Les: Yes I have implemented a similar structure to that listed above, this
is working well and I am able to bring up all drawings with the relevant
revisions in queries.
[color=blue]
> Perhaps you could explain the logic of the grid shown above. You have
> columns headings with dates (e.g. 17 June 2002) and then show every
> drawing below listing the revision letter on this date. Perhaps I have
> missed something, but I can't see how that would be useful, unless all
> drawings are updated on the same date.[/color]
Les: The drawings are not updated on the same date, we may be issued a
drawing on date n and another on date n+5. However we may have a
construction issue on a drawing and require that particular drawing to be
revised to take into consideration the issues that arose, thus having
another issue of the drawing, on another date. This does not mean that
other drawings are updated as they are still on the same issue/revision. if
the revision letter was issued for each drawing on heading date, this would
make it more different for quick visual checks.
However is another drawing is issued/revised on the same date it too uses
the same date thus explaining why it looks like all the drawings are
issued/revised on the same day (this is not conveyed well due to the non
fixed font, apologies)
Does this make more sense?
[color=blue]
> I could imagine a grid with revision letters as column headings and the
> drawing numbers as rows. The tabulated data would be dates - the dates on
> which the drawings reached that revision level. This would mean you could
> see at a glance the revision level of any drawing and the date it was last
> changed.[/color]
Les: this is the same principle but I wish to have the column heading as the
date, the row heading the drawing number and drawing issue letter in the
grid as this method take less space on the paper.
[color=blue]
>
> "Les" <nospam@nospam.spam> wrote in message
> news:d07qvr$v10$1@news.freedom2surf.net...[color=green]
>> Hi can anyone help me,
>>
>>
>>
>> I have just graduated and have started working for a building developer
>> which deals with a large quantity of drawings. As you can imagine these
>> all need documenting and revision of drawings kept a track of. I have
>> recently taking over the administration of the drawings and their current
>> system is not capable of easily managing the data so I have taken it upon
>> myself to try and organise the data in a database. The problem arises
>> when displaying the drawing numbers with the revision dates and revision
>> letters like below in a grid fashion.
>>
>>
>>
>> Day 1 17 9 20 11
>>
>> Month 3 6 8 1 5
>>
>> Year 02 02 03 04 04
>>
>> Drawing Num
>>
>> Drw1 - A B
>>
>> Drw2 - A B C
>>
>> Drw3 - A B
>>
>> Drw4 -
>>
>>
>>
>> I have studied database systems during my degree (IT related) but either
>> I have forgotten or not come across how to do this.
>>
>>
>>
>> If anyone can help my by either pointing in a direction of where to look
>> or similar databases that use a similar grid technique I would be very
>> grateful, I'm not stupid and am prepared to put the work in to get the
>> right result.
>>
>>
>>
>> One last thing, as this is being used in an office I only have access to
>> limited facilities and software that is on offer so the only database
>> available is MS Access XP, very annoying having studied and worked with
>> Oracle.
>>
>>
>>
>> Thanks in advance
>>
>>
>>
>> Les[/color]
>
>
>
>
>[/color]
| 
