| re: Question on Access 2002/2003
"Tom van Stiphout" <no.spam.tom7744@cox.net> wrote in message
news:lvg192d0vp773vgebrvbhcma7jlbhl884i@4ax.com...[color=blue]
> On Wed, 14 Jun 2006 22:53:30 GMT, "Blaine Manyluk"
> <bslaisne@correct.ab.ca> wrote:
>
> The A2K file format is available for Access 2000 - 2003.
> Access 2002 or better is needed to use the Printer object,
> regardless of what file format the database is in.[/color]
Does that mean that an application in A2K file format can run
in A03, and use the Printer object? (Of course it can't
run in A2K unless Printer-object-using code is removed.)
Some other questions:
Do Reports need to be opened in Design mode in A03 to apply
Printer-related property changes (as it does in A2K with
DevMode) even if such changes are temporary?
What if the app is read-only and/or MDE?
What about Access Runtime in A03? Can it do what I suggest
with Printer object, or would that be considered "development"
and disallowed?
Thanks,
Blaine
[color=blue][color=green]
>>Greetings...
>>
>>I have what may seem like silly questions, but I need to have the
>>facts before I proceed with my decision.
>>
>>Access 2002 and 2003 can run (and modify) A2K DBs/apps without
>>having to convert them to the newer version. Is this true?
>>
>>Can an A2K app use the A2/3 Printer objects and still be A2K,
>>or does it need to be converted to A2/3?
>>
>>If it needs to be converted, how easy and reliable is such a
>>conversion, for large complex applications? What about backward
>>compatibility? Any specific issues I need to worry about?[/color][/color]
================================================== ====================
[To reply, remove the S's from my address, and change the R's to N's.]
| 
