No approach yet

[Zebulon]

Hi,

i need an approach to solve this:

i have one table containing 100 fields representing bookable beds in a hostel. These fields are part of an occupation layout showing us which beds are free etc. I have created a 2nd table containing the same fields (name wise) working as "switches" to mark beds to be shown as occupied- these fields are automatically filled with an particular string. The required step is to copy this string from all fields in table 2 containing it to the corresponding fields in table1. This must be done for as many datasets as days are booked. The start date and end date data is to be taken from another table.

I hope this is more or less understandable...and please excuse bad english if there is any as well as wall of text -)

Michael

[comment]

i have one table containing 100 fields representing bookable beds in a hostel.

That's not a good starting point. Try a table of Beds, where each bed is an individual record. Then a second table of Bookings, with fields for BedID, StartDate and EndDate.

[Zebulon]

It is exactly like this.

[comment]

:qwery:

You said 100 fields - I said 100 records.

[Zebulon]

sorry, it is quite late here -) unfortunately i can not display the objects i need to visualize single beds using records- i need fields to do this. the records represent the days of the year. not sure if i made the starting point clear enough?

[comment]

Actually, I didn't understand anything beyond the sentence I quoted. Is the purpose of your solution to track bookings of the beds - or is it only to build a particular type of display? If the former, you should start with a solid data structure, and figure out the display part later. And I am convinced that whatever the desired display is, it CAN be done with records.

[Zebulon]

Actually, I didn't understand anything beyond the sentence I quoted.

uhh, i was not aware my english sucks so much -(

I try to be better: it is all about realizing an particular display now, starting from an existing and hopefully more or less properly designed data structure. Layout

What you see is the target layout/table enabling db users to get an quick overview of the situation. This layout has to display the location of the rooms inside the house as well, sorry i forgot to mention that. i have no clue how that could be done using records, do not forget a lot of different data will cumulate in that view.

cheers, michael

[comment]

It's not a language problem. I don't understand why you need to "copy this string from all fields in table 2 containing it to the corresponding fields in table1." It would also help if you gave your tables some meaningful names, so that we can better understand the underlying issue.

I think you now have a table where each record is a day, and it has 100 fields for 100 rooms - each field noting the status of one room for that day.

If so, why not simply show the records from this table?

---

BTW, you may find that displaying ~300 status fields could be somewhat slow to draw.

[Zebulon]

I don't understand why you need to "copy this string from all fields in table 2 containing it to the corresponding fields in table1."

Table2 = "UserInterfaceAssign" It shall be used to mark beds "occupied". The fields are defined to be filled on click with a string containing data bits from 3 different fields, string to be used later for conditional field formatingin table1 . There is no relation to any start/end date of the booking transaction, it is just to assign the beds and prepare the field contents.

Table1 = "ReservationOverview". It is used just for visualization. Each day is one record containing a field for each bed. This is what you see in the linked pic, previous post.

think you now have a table where each record is a day, and it has 100 fields for 100 rooms - each field noting the status of one room for that day.

Exactly! This is table "ReservationOverview"

so, why not simply show the records from this table?

The data is not yet there -)

Given Situation: A group has booked 40 beds for 10 days. In case you would assign the beds manually as it is today you would have to touch 400 field entries... and you will make mistakes resulting in inconsistent data. So, what i want to achieve is to "preselect" the beds and then run a script to beam the bed´s status to each related day of the booking transaction.

I hope i was able to explain a bit better now.

BTW, you may find that displaying ~300 status fields could be somewhat slow to draw.

Ah, no - in a different view i display far more fields without any noticeable slowness. FM server running on mac mini.

Many thanks for your efforts and, again please excuse any inaccuracy.

Edited October 22, 2010 by Guest

[comment]

Table2 = "UserInterfaceAssign" It shall be used to mark beds "occupied".

What does a record in this table represent?

The fields are defined to be filled on click with a string containing data bits from 3 different fields, string to be used later for conditional field formatingin table1 .

Please elaborate.

There is no relation to any start/end date of the booking transaction, it is just to assign the beds and prepare the field contents.

This too is not clear.

A group has booked 40 beds for 10 days.

Will you always assign them the same 40 beds for the entire 10 days?

[comment]

BTW, I suggest you explore the attached file.

ViewBookings.zip