George,
you are not missing anything here. This is the consequence of not using the
Designer, which adds some properties as name etc. to the object contained in
the designer object. In fact, when you query the report for its name
property when
you instantiated a report object via loading a .rpt file through the
application object, then you will get a VB#438 error.
The name property is a feature of the designer object.
Unfortunately there is no way of identifying the report fields in the report
definition in such a way that you can find out what is what in your
VB-environment.
Fred
Quote:
>I have been trying to use text objects with the VB6 and the CR8 developer
>edition. I want to be able to load external .rpt files at run time rather
>than linking the report designer files at build time. The reason foir this
>is that I want to use the stand-alone CR report designer to make minor
>modifications to the report layouts for different customers, etc.
>One big problem I have run into is that I can't get the standalone designer
>to save text object names, and I can't find any way to give text object
>names other than with the VB embedded designer. Am I missing something
here,
>or should I try to find another way to do what I want?
>Thanks!
>--
>-----------------------------------
>Elias Sports Bureau