Re: storage status

Thanks very much. Nice with a real example of how to solve the problem.
I will try to build something like it since I think it will fullfill my
needs.

best regards, Tom

"Dan Fretwell" <dan@xxxxxxxxxxxxx> skrev i en meddelelse
news:1136024886.534424.140440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi Tom
>
> My location table has two fields: DiskID; Location
>
> The DiskID is the ID number of the CD currently in the location. If
> there is no CD in the location then I set DiskID to -1.
> Location is the description of the location which allows you to
> physically locate it. In my case this is a set of "coordinates", for
> example: 1.2.08 which tells me that the CD is in Box1, Tray2 and index
> number 8. In order to preform this table I created a new record for
> each location and set the DiskID field equal to -1. Because of the
> nature of my locations I was able to do this via a script doing a
> triple loop through the possible index numbers; tray numbers and box
> numbers. If you do not have a simple description of the locations then
> you may have to do this by hand, or, if you already have all the
> locations in a table then make a copy, delete all the other fields and
> then add in the DiskID field.
>
> The match between the item table and location table is via the DiskID
> number, not the location. This enables you to change the description of
> a location, move a CD from one location to another, remove a CD from a
> location just by manipulation of the DiskID number. In the data entry
> table for a new CD I have a portal pointing to the empty locations. I
> have an assign button alongside each entry and clicking that runs a
> script which assigns the CD to that location.
>
> [The empty locations table requires that you find all locations with
> DiskID = -1. I don't know the simplest way of doing this - perhaps
> someone else could chip in. The method I use is to have a global field
> g_minus which is a calculation equal to -1 (I keep globals in a
> separate table so this is in a table Settings). I then relate my CD
> table to the Settings table by x (all-match-all) and relate the
> locations table to Settings by matching g_minus to DiskID. A portal
> into this relationship from CD table list all empty locations. If you
> want them in a particular order then you can sort the portal, or sort
> the relationship.]
>
> The advantage of using the DiskID number for the match is that if you
> have other related data then a change of location doesn't alter that
> relationship and reflects the fact that a storage location is not an
> intrinsic property of an item.
>


.

Quantcast