Labels in Access runtime 2007

[Mark Andrews]

I'm looking for a good way to add label functionality to an application I
wrote in Access2007 (distributed using the runtime). I would like to
somehow cover all possible labels the user might have.

Option #1:
- call the label wizard (doesn't work in runtime)

Option #2:
- write a whole bunch of reports (one for each style of label)
Wondering how many that might be?

Option #3:
- Use Microsoft word merging to create labels
Seems a little too difficult for the user

Option ???:
Wondering if there is a better approach anyone has used?

Thanks in advance,
Mark

 

[Jeanette Cunningham]

Have a look at the sample db here
http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=319

There are also sample db's for batch offset labels.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Mark Andrews]

Thanks. That example is ok in that it shows how to do offset labels and
many labels of the same data.

have any examples that show how to handle 200 different label sizes or
things of that nature.
Without using the label wizard (which doesn't work in the runtime).

Thanks,
Mark

 

[Jeanette Cunningham]

Not that I know of.
Unless someone else knows better, I would think that you would need a
separate report for each label size.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Larry Linson]

Not that I know of.
Unless someone else knows better, I would
think that you would need a separate report
for each label size.

It would be possible to re-create the Label Wizard or to create a Wizard
that would run in the runtime. You can perform design functions from code,
if you need to, but you just can't SEE design view.

Frankly, unless I was being hired by Avery or some other label manufacturer,
I would reject a requirement for "any" or "all" kinds of labels, and
presumably, requiring the ability to do rich- text content, as well. I'd
reject it on the basis that it could be a valid requirement for a label
manufacturer, and such a company might be willing to pay the price; but it's
unlikely to be a valid requirement for any other business application, that
they had not thought the matter through and should know that it would be
quite expensive.

I'd relent if they wanted to pay me to write up the requirements and design,
at which point I could give them a good estimate (not a fixed price!) as to
what it would cost to implement. My guess is, they'd have to want it very
badly, very badly indeed, to consider paying what I think it would cost.

Sounds like a typical manager or user who has no idea how much work would
have to go into something like that, thinking that they can get it "on the
cheap".

Larry Linson
Microsoft Office Access MVP