Re: Access 2000 Find Inbox at Runtime

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Bob Dydd (smileyBob_at_hotmail.com)
Date: 08/01/04 

Date: Sun, 01 Aug 2004 14:17:18 GMT

On Fri, 30 Jul 2004 19:01:03 GMT, Tony Toews <ttoews@telusplanet.net>
wrote:

Hi All

Thanks to everyone that answered

We have the Access 2000 developers edition and have distributed a few
with the "Package and Deployment manager (PDM). but most users are
having difficulty with relinking the backend AND finding and Linking
the Inbox.

I am using a linking form that I bought from Database Creations. THis
has all the code in the code behind forms to refresh links and is able
to cope with more that one back end. .... The difficulty is that it
"sees" the inbox as a table that it cannot link to and produces an
error. So I am a bit stuck there as well.

If anyone has any pointers I would be most grateful.

The PDM that is supplied with ODE is NOT a great piece of Kit. IMHO.
Barely adequate. So before further redistribution this will have to be
replaced.

Reading through the groups, the bulk of opinion seem to be to use
Installshield in conjuction with Sage Scripts, but I have yet to try
this out. About $900 to find the answer to that one, Whew!!

>Bob Dydd <smileyBob@hotmail.com> wrote:
>
>>I have an Access 2000 MDB with the Usual FrontEnd/BackEnd Arrangement.
>>The program depends on being able link to "Inbox" in Ms Outlook 2000.
>>
>>This is easy enough to do from the FrontEnd and has been OK while me
>>and the missus have been using the program ourselves.
>>
>>Now We want to be able to give the program to others who mainly do
>>not have MS Access installed., or if they do, have no idea what it is
>>about
>
>For those without the runtime you need to use the MOD to create a runtime. Trouble
>is it has problems when distributed to sites running different versions of software
>and may no longer be available for A2000.
>
>Microsoft Access (Office) Developer Edition FAQ
>http://www.granite.ab.ca/access/developereditionfaq.htm
>
>>To make matters worse some are using different versions of MS Outlook
>>MS Outlook 2003 50%
>>MS Outlook 2002 25%
>>MS Outlook 2000 25%
>
>Late binding means you can safely remove the reference and only have an error when
>the app executes lines of code in question. Rather than erroring out while starting
>up the app and not allowing the users in the app at all. Or when hitting a mid, left
>or trim function call.
>
>You'll want to install the reference if you are programming or debugging and want to
>use the object intellisense while in the VBA editor. Then,. once your app is
>running smoothly, remove the reference and setup the late binding statements.
>
>Sample code:
>' Declare an object variable to hold the object
>' reference. Dim as Object causes late binding.
>Dim objWordDoc As Object
>Set objWordDoc = CreateObject(" Word.Document")
>
>For more information including additional text and some detailed links see the "Late
>Binding in Microsoft Access" page at http://www.granite.ab.ca/access/latebinding.htm
>
>Tony

Relevant Pages

  • Re: Access 2000 Find Inbox at Runtime
    ... We have the Access 2000 developers edition and have distributed a few ... The PDM that is supplied with ODE is NOT a great piece of Kit. ... >up the app and not allowing the users in the app at all. ... >You'll want to install the reference if you are programming or debugging and want to ...
    (microsoft.public.outlook.program_vba)
  • Re: Access 2000 Find Inbox at Runtime
    ... We have the Access 2000 developers edition and have distributed a few ... The PDM that is supplied with ODE is NOT a great piece of Kit. ... >up the app and not allowing the users in the app at all. ... >You'll want to install the reference if you are programming or debugging and want to ...
    (microsoft.public.outlook.interop)
  • Re: How do I find the Path for Win.Word?
    ... For example, Bryan's reply to your original message was bottom-posted, meaning he quoted your message and wrote his reply UNDER what he quoted. ... You *should* be OK with a reference to Word 10 and your app being run on a system with Word 11 installed. ... I've written many little apps and even quite large apps that use Automation with various Office products and I've had VERY few problems with those apps working when a different version of Office is installed. ... However, in almost all of these, it's because they've developed using a later version of Office and uses features specific to that version, and then the app doesn't work with an earlier version of Office. ...
    (microsoft.public.vb.general.discussion)
  • Re: Trying to use unmanaged with C#
    ... And you're doing this from an ASP.NET app? ... It only became the need to be a .NET object when I "imported" it into my ... The object houses all the protocol for clients. ... if you *do* need to pass a reference of some .NET class to a COM ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Visual Basic Ver 6.0 - Word 2003
    ... able to reference the 9.0 object library (on your dev PC if it has Word 2000 ... installed) and your app should work on a target PC even if Office 2003 is ... installed on the target PC. ... I think you need to pinpoint the line of code causing the error. ...
    (microsoft.public.vb.general.discussion)