Re: Stephen Lebans Report2PDF



Stephen

This post lead me to your site to have a look at your solution, as I have
yet to find an adequate one size fits all method of creating PDF's from
Access. Virtually every customer I have is using different PDF creators, or
different versions of the same software, all of which seem to have
idiosyncrasies. I am forever having to tweak this and change that to make
things work. What's worse it makes me look as if I do not know what the
heck I am doing. This is something that OUGHT TO BE EASY to implement, but
trips me up almost all of the time.

This solution looks VERY promising and I am willing to buy the DynaPDF tool
if I can get the glue you used to hook Access Reports and Snapshots up to
it. I have downloaded their Eval an looked at the documentation and VB
examples. I find that is architected similar to but with much more control
and complexity than a Package I already own (DynammicPDF). The fact that it
is an Xcopy install makes it even more interesting.

I am having problems with the Access2K version that I downloaded from your
site. It complains:

fCreateSnap.fParseSnap:-2147220958
Sorry...Page size not supported
Please select a different Report to Export

No matter what I throw (Report or existing Snapshot) at it I get this same
message. I have tried using it directly from the example you provided in
the mde, and as an external library to one of my projects. I thought
perhaps a problem with A4 vs. Letter Page setups, but no joy.

So I guess the questions are:
1) Is there a known problem with the Access 2K version
2) Are you willing to share the Access to DynaPDF source WITHOUT the
DynaPDF License Key
3) Would you be willing to give us a hint of how the glue works so I
could attempt to come up with an independent solution.

>From my short observation it appears that you may be parsing a snapshot of
the report, and translating the objects that you find there, into calls to
the DynaPDF library. Can you point me to any good documentation of how to
parse the snapshot format? I would most appreciative of any help you can
provide.

Thanks
--
Ron W
www.WorksRite.com
"Silvester" <spamblock@xxxxxxxx> wrote in message
news:uoDuw1Y4FHA.3000@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> With reference to Stephen Lebans interesting report to PDF solution found
at
> http://www.lebans.com/reporttopdf.htm
>
> If reference is set to the provided mde and the app is distributed along
> with the mde & dll in the app's default directory, will I run into broken
> reference issues on end user machines?
>
> Basically I'm asking how to set up references to this mde so that it can
be
> safely distributed.
>
> TIA
>
>


.



Relevant Pages

  • Re: MDB to MDE trouble
    ... AFAIK an MDE can't reference an MDB. ... You have to parse this startparam while report.mdb is loading and can then decide inside your report.mdb what report with what additional params it should to open. ...
    (comp.databases.ms-access)
  • Re: Helmets +/- Safety
    ... The DfT report makes ... I think that reference 4 is of major significance although you may have ... laws - not review the efficacy of cycle helmets / head injuries. ... weighed against the costs. ...
    (uk.rec.cycling)
  • ANS: Erroneous Compiler Errors When Building
    ... will sometimes report a selection of errors that are quite false. ... a reference to another assembly when it already has a reference. ... It turns out that the fault lies with the compiler. ... as the compiler will not build assemblies that haven't changed (I ...
    (microsoft.public.dotnet.languages.vb)
  • Re: DH Query By Form
    ... Did you set a reference to the DAO ... Are you getting any other errors after clicking the Run Report button? ... I modified this query to reference my table, ... Duane Hookom wrote: ...
    (microsoft.public.access.queries)
  • Re: The Asymmetry of Identity
    ... Nobody wants sqrt4, a reference, for its own sake. ... analyze them a bit further to get meaning that wasn't already evoked ... report reports external properties. ... survey to others. ...
    (sci.logic)