serialize/deserialize Access report object

[Graham]

I'd like to automate delivery of new Report objects to my users (note:
NOT published reports -- the report *objects* themselves.) I could
fairly easily write code to capture the appropriate properties of the
report and write it to a file, and then code on the other side to read
the file and create a report. E.g.,

<REPORT>
<NAME>My Report</NAME>
<CONTROLS>
<CONTROL>
<NAME>Label1</NAME>
<TYPE>acLabel</TYPE>
<POSITION>1,1</POSITION>
</CONTROL>
....

and so on. It strikes me, though, that someone must have written this
code already. I've googled around a bit, but can't find anything. Any
help?

Thanks,

g.

[Rick Brandt]

Graham wrote:

I'd like to automate delivery of new Report objects to my users (note:
NOT published reports -- the report *objects* themselves.) I could
fairly easily write code to capture the appropriate properties of the
report and write it to a file, and then code on the other side to read
the file and create a report. E.g.,

<REPORT>
<NAME>My Report</NAME>
<CONTROLS>
<CONTROL>
<NAME>Label1</NAME>
<TYPE>acLabel</TYPE>
<POSITION>1,1</POSITION>
</CONTROL>
...

and so on. It strikes me, though, that someone must have written this
code already. I've googled around a bit, but can't find anything. Any
help?

Thanks,

g.

Access has built in (though undocumented) functions for this.

SaveAsText(ObjectType as Long, ObjectName As String, FileName As String)

LoadFromText(ObjectType as Long, ObjectName As String, FileName As String)

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Graham Charles]

Outstanding (the functions) and astounding (that they're not
documented).

Thanks a lot!

[Larry Linson]

"Graham Charles" <gr****@aiid.com> wrote

Outstanding (the functions) and astounding (that
they're not documented).

Not so astounding. It is very common for software to include undocumented
functionality -- undocumented is also "unsupported", and often means "not
thoroughly tested". It is (as I would guess these to be, because they have
been around for a long time) often for the use of that software's
developers, or something that "didn't quite make the release".

Larry Linson
Microsoft Access MVP

[Tom van Stiphout]

On Sat, 24 Dec 2005 20:06:00 GMT, "Larry Linson"
<bo*****@localhost.not> wrote:

These are probably the exception of the "not tested" rule, since they
are used by the SourceSafe integration.

-Tom.

"Graham Charles" <gr****@aiid.com> wrote

Outstanding (the functions) and astounding (that
they're not documented).

Not so astounding. It is very common for software to include undocumented
functionality -- undocumented is also "unsupported", and often means "not
thoroughly tested". It is (as I would guess these to be, because they have
been around for a long time) often for the use of that software's
developers, or something that "didn't quite make the release".

Larry Linson
Microsoft Access MVP