Crestron
e-control Vote SW-VOTE
52
••
Database
Installation & Reference Guide — DOC. 5822
Database
In the present release, a single database file is named in the
COM Settings
tab of the
Configuration Options
window. This one file is used as the sole source of all
database tables for all the signal blocks in the configuration.
Database Tables
This section discusses the database tables accessed by the various signal blocks of
the SW-VOTE component of the Crestron Software Server.
In the following table, for a given RTS Console:
Let
q
= the size of the queue set (
i.e.,
the number of queues defined)
Let
f
= the number of “save files” defined.
Database tables used by SW-VOTE component
Signal
Block
Tables used
How used
Queries
Each scroller references a record from this
table (using the
ID
field as a key); the record
is used to form a query to be “bound” to the
scroller
Scroller
Each scroller’s query
references (an) arbitrary
table(s)
As the data source of the query bound to
scroller
Members
Sent to control system upon receipt of the
SendNames
signal
Voting
Console
Agenda
By data-bound control in
Vote Proctor
window;
used to select an agenda item prior to a vote
By scroller from control system; used to select
an agenda item prior to a vote
Members
Sent to control system upon receipt of the
SendNames
signal
As the data source for seat names (and
possibly other information) when adding
records to the queue tables
A set of
q
scroller tables
As “queue tables” (to implement queues)
Request-
to-Speak
Console
q
sets of
f
additional scroller
tables
As “save files” (to implement saving and
reloading of queue sets)
The Queries table can be viewed and edited with the
Database | Table
command;
the Members and Agenda tables can be viewed with the
Voting | Tables
command.
The remaining tables (which are the request-to-speak queue scroller tables and the
timetable) are not routinely viewed or edited. To create the tables, you will need
Microsoft Access. Or, you can repurpose a copy of the supplied sample database file
which contains three queues
x
9 save files.
Naming of tables
The names of the
Queries
,
Members
, and
Agenda
tables are fixed in the
present release.
*
The other table names are derived from queries formed from records
* Having fixed members and agenda table names effectively precludes using a single server configuration for more than one “room” (or body) at the
same time. A future release may remove this limitation. In the mean time, different bodies meeting at different times can be served by pointing to
