Access 2007 Report Formatting...

[lupo666]

Hi everybody, this time I have three problems driving me nuts :-(((

(1)

I have a report with 20 or so Yes/No "squares". Is there a way to
either hide/show the "square" or change the yes/no relative textbox,
depending on value?

(2)

Is there a way to insert a page break, so that some fields will be on
page 1 and some on page 2; so that a report based on three records,
for example, will print on 6 pages and so forth?

(3)

The database is now installed on a server and three clients are
successfully inserting data into it. One worker wants to input data at
home, on a local copy, and then "sync" the inputed data on the server.
Is there a safe (speed not important) way to do this?

Thank u in advance for any u may provide...

Regards, Lupo

[Allen Browne]

Answers in-line.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"lupo666" <lu*****@gmail.comwrote in message
news:11**********************@k35g2000prh.googlegr oups.com...

Hi everybody, this time I have three problems driving me nuts :-(((

(1)

I have a report with 20 or so Yes/No "squares". Is there a way to
either hide/show the "square" or change the yes/no relative textbox,
depending on value?

See:
Format Check boxes on reports
at:
http://allenbrowne.com/ser-52.html
The article explains how to use a text box bound to a WingDings symbol to
display a yes/no field any way you want, any size, color, or even
conditionally format.

If you have 20 yes/no fields in the one table, there's a very good chance
that this would be better represented as many *records* in a related table,
rather than as many yes/no fields in the one table. More info:
Don't use Yes/No fields to store preferences
at:
http://allenbrowne.com/casu-23.html

(2)

Is there a way to insert a page break, so that some fields will be on
page 1 and some on page 2; so that a report based on three records,
for example, will print on 6 pages and so forth?

Let's assume this report is based on a table that has a primary key field
named ID. In report design view, open the Sorting And Grouping box (View
menu.) Enter the ID field in the dialog on its own row (i.e. below any
others you have there.) Then in the lower pane of the dialog, choose Yes for
the Group Footer property. Access adds an ID Group Footer to the design.
Place the 2nd lot of fields into this section, and you can print this on a
2nd page.

(Since the ID is unique for every record, this group footer repeats for
every record, giving you 2 sections for every record.)

(3)

The database is now installed on a server and three clients are
successfully inserting data into it. One worker wants to input data at
home, on a local copy, and then "sync" the inputed data on the server.
Is there a safe (speed not important) way to do this?

There are several possibilities.

The simplest is to copy the data file to a memory stick, take it home, edit
it, and then bring it back and replace the original. (Whether you consider
that safe is up to you.)

Another possiblity is replication. The database does need to be designed
from the ground up with replication in mind to use this properly, and may
still be some work in manually resolving conflicts (e.g. where the person
returns from home after editing Fred Nerk's record and the software tells
him that someone at work also edited that record while he was out.) Most
signficantly, Access 2007 does not handle replication, so this may not be a
good idea in view of the future of Access.

Another possibility might be logging in from home over a VPN session into
Terminal Server or Citrix. Albert Kaqllal has info about running Access over
a Wide Area Network:
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Hopefully you have already split the database.

Thank u in advance for any u may provide...

Regards, Lupo

[lupo666]

Dear Allen,

first of all, thank you for your quick and very complete reply. The
database in question has been split on creation (u helped a long time
ago on a different question on updating and I have been designing
split DBs ever since: one DATA.MDB and one INTERFACE.MDB.
INTERFACE.MDB always points to "Z:" for data location and I just copy
it to the different clients and make "Z:" the network location of
DATA.MDB, a SUBST, basically...).

This database is for a small company that handles firedoors
installation and maintenance. So, each client has a number of doors
and each door has 20 or so possible accessories/characteristics...
(please, see #2...)

(1) Your solution is PERFECT! For my client's needs, I need to add two
textboxes for each "accessory/characteristic" (one for text, one for
box), so I can gray out the "false" text or bold the "true" one AND
leave empty/"square" for the box... WONDERFUL!!!

(2) Your solution for NOT using Yes/Nos is practical and certanly more
"relational", but, in this case, it would require an input form with
two subform (Client >Door >Accessories) and would require the
worker to select the door first and then the accessories... knowing
the people who input the data, it would spell errors, errors,
errors... I will certanly keep the "trick" for another project...

(3) DB is split (see intro...) and my first idea was VPN, but it's
rather slow... Replication has been dropped in 2007 and was already
prone to errors in previous versions (know by experience...). Since
there is one worker who is a bit more into computers, what if the
worker working from home always works with an EMPTY DATA.MDB and then
the tables in it are copied/pasted into the main one thru a usb key?
The worker only inputs new data, never works on old ones...

Thank you again for your help. One day I will visit Australia and I'll
surely pass by. In the meanwhile, should u ever be in Italy, come by,
you'll be most welcome!

Ciao, Lupo

On Oct 14, 10:41 am, "Allen Browne" <[e-mail]>
wrote:

Answers in-line.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"lupo666" <[e-mail] in message

news:11**********************@k35g2000prh.googlegr oups.com...

Hi everybody, this time I have three problems driving me nuts :-(((

(1)

I have a report with 20 or so Yes/No "squares". Is there a way to
either hide/show the "square" or change the yes/no relative textbox,
depending on value?

See:
Format Check boxes on reports
at:
http://allenbrowne.com/ser-52.html
The article explains how to use a text box bound to a WingDings symbol to
display a yes/no field any way you want, any size, color, or even
conditionally format.

If you have 20 yes/no fields in the one table, there's a very good chance
that this would be better represented as many *records* in a related table,
rather than as many yes/no fields in the one table. More info:
Don't use Yes/No fields to store preferences
at:
http://allenbrowne.com/casu-23.html

(2)

Is there a way to insert a page break, so that some fields will be on
page 1 and some on page 2; so that a report based on three records,
for example, will print on 6 pages and so forth?

Let's assume this report is based on a table that has a primary key field
named ID. In report design view, open the Sorting And Grouping box (View
menu.) Enter the ID field in the dialog on its own row (i.e. below any
others you have there.) Then in the lower pane of the dialog, choose Yes for
the Group Footer property. Access adds an ID Group Footer to the design.
Place the 2nd lot of fields into this section, and you can print this on a
2nd page.

(Since the ID is unique for every record, this group footer repeats for
every record, giving you 2 sections for every record.)

(3)

The database is now installed on a server and three clients are
successfully inserting data into it. One worker wants to input data at
home, on a local copy, and then "sync" the inputed data on the server.
Is there a safe (speed not important) way to do this?

There are several possibilities.

The simplest is to copy the data file to a memory stick, take it home, edit
it, and then bring it back and replace the original. (Whether you consider
that safe is up to you.)

Another possiblity is replication. The database does need to be designed
from the ground up with replication in mind to use this properly, and may
still be some work in manually resolving conflicts (e.g. where the person
returns from home after editing Fred Nerk's record and the software tells
him that someone at work also edited that record while he was out.) Most
signficantly, Access 2007 does not handle replication, so this may not be a
good idea in view of the future of Access.

Another possibility might be logging in from home over a VPN session into
Terminal Server or Citrix. Albert Kaqllal has info about running Access over
a Wide Area Network:
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Hopefully you have already split the database.

Thank u in advance for any u may provide...

Regards, Lupo- Hide quoted text -

- Show quoted text -

[Allen Browne]

Okay, looks like you've digested all of that.

If the worker-from-home is just adding records (no need to see existing
ones), you could give her an empty data mdb and import from there
periodically (emptying out this db again.) The main issue would be making
sure that the related records get the correct new key values.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"lupo666" <lu*****@gmail.comwrote in message
news:11*********************@t8g2000prg.googlegrou ps.com...

Dear Allen,

first of all, thank you for your quick and very complete reply. The
database in question has been split on creation (u helped a long time
ago on a different question on updating and I have been designing
split DBs ever since: one DATA.MDB and one INTERFACE.MDB.
INTERFACE.MDB always points to "Z:" for data location and I just copy
it to the different clients and make "Z:" the network location of
DATA.MDB, a SUBST, basically...).

This database is for a small company that handles firedoors
installation and maintenance. So, each client has a number of doors
and each door has 20 or so possible accessories/characteristics...
(please, see #2...)

(1) Your solution is PERFECT! For my client's needs, I need to add two
textboxes for each "accessory/characteristic" (one for text, one for
box), so I can gray out the "false" text or bold the "true" one AND
leave empty/"square" for the box... WONDERFUL!!!

(2) Your solution for NOT using Yes/Nos is practical and certanly more
"relational", but, in this case, it would require an input form with
two subform (Client >Door >Accessories) and would require the
worker to select the door first and then the accessories... knowing
the people who input the data, it would spell errors, errors,
errors... I will certanly keep the "trick" for another project...

(3) DB is split (see intro...) and my first idea was VPN, but it's
rather slow... Replication has been dropped in 2007 and was already
prone to errors in previous versions (know by experience...). Since
there is one worker who is a bit more into computers, what if the
worker working from home always works with an EMPTY DATA.MDB and then
the tables in it are copied/pasted into the main one thru a usb key?
The worker only inputs new data, never works on old ones...

Thank you again for your help. One day I will visit Australia and I'll
surely pass by. In the meanwhile, should u ever be in Italy, come by,
you'll be most welcome!

Ciao, Lupo

On Oct 14, 10:41 am, "Allen Browne" <[e-mail]>
wrote:

>Answers in-line.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"lupo666" <[e-mail] in message

news:11**********************@k35g2000prh.googleg roups.com...

Hi everybody, this time I have three problems driving me nuts :-(((

(1)

I have a report with 20 or so Yes/No "squares". Is there a way to
either hide/show the "square" or change the yes/no relative textbox,
depending on value?

See:
Format Check boxes on reports
at:
http://allenbrowne.com/ser-52.html
The article explains how to use a text box bound to a WingDings symbol to
display a yes/no field any way you want, any size, color, or even
conditionally format.

If you have 20 yes/no fields in the one table, there's a very good chance
that this would be better represented as many *records* in a related
table,
rather than as many yes/no fields in the one table. More info:
Don't use Yes/No fields to store preferences
at:
http://allenbrowne.com/casu-23.html

(2)

Is there a way to insert a page break, so that some fields will be on
page 1 and some on page 2; so that a report based on three records,
for example, will print on 6 pages and so forth?

Let's assume this report is based on a table that has a primary key field
named ID. In report design view, open the Sorting And Grouping box (View
menu.) Enter the ID field in the dialog on its own row (i.e. below any
others you have there.) Then in the lower pane of the dialog, choose Yes
for
the Group Footer property. Access adds an ID Group Footer to the design.
Place the 2nd lot of fields into this section, and you can print this on
a
2nd page.

(Since the ID is unique for every record, this group footer repeats for
every record, giving you 2 sections for every record.)

(3)

The database is now installed on a server and three clients are
successfully inserting data into it. One worker wants to input data at
home, on a local copy, and then "sync" the inputed data on the server.
Is there a safe (speed not important) way to do this?

There are several possibilities.

The simplest is to copy the data file to a memory stick, take it home,
edit
it, and then bring it back and replace the original. (Whether you
consider
that safe is up to you.)

Another possiblity is replication. The database does need to be designed
from the ground up with replication in mind to use this properly, and may
still be some work in manually resolving conflicts (e.g. where the person
returns from home after editing Fred Nerk's record and the software tells
him that someone at work also edited that record while he was out.) Most
signficantly, Access 2007 does not handle replication, so this may not be
a
good idea in view of the future of Access.

Another possibility might be logging in from home over a VPN session into
Terminal Server or Citrix. Albert Kaqllal has info about running Access
over
a Wide Area Network:
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Hopefully you have already split the database.

Thank u in advance for any u may provide...

Regards, Lupo- Hide quoted text -

- Show quoted text -

[lupo666]

I have read a lot of your posts and the one you helped me with last
time and tried to follow as much as I could...

For the key values, I thought of that in advance: even though it's not
proper databasing, I use the client's name as primary key (clients
with different branches will have suffixes like "Client - Perth",
"Client - Melbourne", "Client - Sydney"...). This way, instead of
trying to understand non-matching autonumbers, the conflicting fields
will have clear names...

Thank you, again, I really mean it. You are doing a wonderful thing
for a lot of people like me...

Regards, Lupo

On Oct 15, 4:12 pm, "Allen Browne" <[e-mail]:

Okay, looks like you've digested all of that.

If the worker-from-home is just adding records (no need to see existing
ones), you could give her an empty data mdb and import from there
periodically (emptying out this db again.) The main issue would be making
sure that the related records get the correct new key values.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"lupo666" <[e-mail] in message

news:11*********************@t8g2000prg.googlegrou ps.com...

Dear Allen,

first of all, thank you for your quick and very complete reply. The
database in question has been split on creation (u helped a long time
ago on a different question on updating and I have been designing
split DBs ever since: one DATA.MDB and one INTERFACE.MDB.
INTERFACE.MDB always points to "Z:" for data location and I just copy
it to the different clients and make "Z:" the network location of
DATA.MDB, a SUBST, basically...).

This database is for a small company that handles firedoors
installation and maintenance. So, each client has a number of doors
and each door has 20 or so possible accessories/characteristics...
(please, see #2...)

(1) Your solution is PERFECT! For my client's needs, I need to add two
textboxes for each "accessory/characteristic" (one for text, one for
box), so I can gray out the "false" text or bold the "true" one AND
leave empty/"square" for the box... WONDERFUL!!!

(2) Your solution for NOT using Yes/Nos is practical and certanly more
"relational", but, in this case, it would require an input form with
two subform (Client >Door >Accessories) and would require the
worker to select the door first and then the accessories... knowing
the people who input the data, it would spell errors, errors,
errors... I will certanly keep the "trick" for another project...

(3) DB is split (see intro...) and my first idea was VPN, but it's
rather slow... Replication has been dropped in 2007 and was already
prone to errors in previous versions (know by experience...). Since
there is one worker who is a bit more into computers, what if the
worker working from home always works with an EMPTY DATA.MDB and then
the tables in it are copied/pasted into the main one thru a usb key?
The worker only inputs new data, never works on old ones...

Thank you again for your help. One day I will visit Australia and I'll
surely pass by. In the meanwhile, should u ever be in Italy, come by,
you'll be most welcome!

Ciao, Lupo

On Oct 14, 10:41 am, "Allen Browne" <[e-mail]>
wrote:

Answers in-line.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"lupo666" <[e-mail] in message

>news:11**********************@k35g2000prh.googleg roups.com...

Hi everybody, this time I have three problems driving me nuts :-(((

(1)

I have a report with 20 or so Yes/No "squares". Is there a way to
either hide/show the "square" or change the yes/no relative textbox,
depending on value?

See:
Format Check boxes on reports
at:
http://allenbrowne.com/ser-52.html
The article explains how to use a text box bound to a WingDings symbol to
display a yes/no field any way you want, any size, color, or even
conditionally format.

If you have 20 yes/no fields in the one table, there's a very good chance
that this would be better represented as many *records* in a related
table,
rather than as many yes/no fields in the one table. More info:
Don't use Yes/No fields to store preferences
at:
http://allenbrowne.com/casu-23.html

(2)

Is there a way to insert a page break, so that some fields will be on
page 1 and some on page 2; so that a report based on three records,
for example, will print on 6 pages and so forth?

Let's assume this report is based on a table that has a primary key field
named ID. In report design view, open the Sorting And Grouping box (View
menu.) Enter the ID field in the dialog on its own row (i.e. below any
others you have there.) Then in the lower pane of the dialog, choose Yes
for
the Group Footer property. Access adds an ID Group Footer to the design.
Place the 2nd lot of fields into this section, and you can print this on
a
2nd page.

(Since the ID is unique for every record, this group footer repeats for
every record, giving you 2 sections for every record.)

(3)

The database is now installed on a server and three clients are
successfully inserting data into it. One worker wants to input data at
home, on a local copy, and then "sync" the inputed data on the server.
Is there a safe (speed not important) way to do this?

There are several possibilities.

The simplest is to copy the data file to a memory stick, take it home,
edit
it, and then bring it back and replace the original. (Whether you
consider
that safe is up to you.)

Another possiblity is replication. The database does need to be designed
from the ground up with replication in mind to use this properly, and may
still be some work in manually resolving conflicts (e.g. where the person
returns from home after editing Fred Nerk's record and the software tells
him that someone at work also edited that record while he was out.) Most
signficantly, Access 2007 does not handle replication, so this may not be
a
good idea in view of the future of Access.

Another possibility might be logging in from home over a VPN session into
Terminal Server or Citrix. Albert Kaqllal has info about running Access
over
a Wide Area Network:
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Hopefully you have already split the database.

Thank u in advance for any u may provide...

Regards, Lupo- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -