[AccessD] Runtime Limitations?

Well with this situation I would be inclined to use late binding, you 
cannot reset missing or mangled  references with an MDE.
as you cannot recompile or change the source p-code cause it ain't there 
anymore. You are also going to have to handle missing objects
as you will probably hit machines missing a Word install or a Net Admin 
that has turned off vb scripting or
access to WSH for security reasons, so your FSO calls will fail. You 
might have to rewrite your FSO methods to use general API calls.

Dan Waters wrote:

>Hello Charlotte,
>
>I know the standard limitations of a runtime version - these are well
>described on the MSDN website.  My applications handle these well.
>
>My goal is to offer the use of runtime versions to clients where they don't
>want to install full versions of Access.
>
>Apparently I read something wrong because when I tested using the /runtime
>switch, API's, FSO, and spellchecking all worked fine.
>
>Thanks,
>Dan
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
>Sent: Friday, May 28, 2004 12:29 PM
>To: Access Developers discussion and problem solving
>Subject: RE: [AccessD] Runtime Limitations?
>
>Not true.  Your references are part of the database, not of Access.  The
>main differences are in some odd places, like the fact the you have to
>specifically set toolbars in code because runtime doesn't recognize the
>property setting and unhandled errors simply dump you out of the
>database.  What is it you want to do?
>
>Charlotte Foust
>
>-----Original Message-----
>From: Dan Waters [mailto:dwaters at usinternet.com] 
>Sent: Friday, May 28, 2004 9:24 AM
>To: 'Access Developers discussion and problem solving'
>Subject: RE: [AccessD] Runtime Limitations?
>
>
>Marty,
>
>I thought I read that I could only use code that is part of Access.  For
>example, no automation of Word, Excel, or other applications.
>
>It wasn't as specific as CurrentDB, or CodeDB (what is CodeDB?).
>
>Do you know where I could find a useful list of the differences between
>runtime Access and the full version?
>
>Thanks,
>Dan
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
>Sent: Friday, May 28, 2004 11:45 AM
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] Runtime Limitations?
>
>Are you referring to the proper use of CurrentDB and CodeDB in addin
>MDE's
>
>Dan Waters wrote:
>
>  
>
>>Hello to All!
>>
>>
>>
>>I seem to remember reading somewhere that when you are using an Access 
>>Runtime installation, you cannot refer to other object models in code.
>>    
>>
>
>  
>
>>Is this correct?  I read a couple of articles in MSDN, but couldn't 
>>find mention of this limitation.
>>
>>
>>
>>I tested using the /runtime switch.  My code uses API's, File System
>>    
>>
>Objects
>  
>
>>(FSO), and spellchecking (Word), and all worked fine.
>>
>>
>>
>>TIA,
>>
>>Dan Waters
>>
>>
>>
>> 
>>
>>    
>>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada