From: Sylvain Lafontaine on 23 Nov 2009 13:54
You should perform this step everytime there is a big change in Windows (new
service pack, new version of Office, etc.) or when you are copying the MDFB
file to another machine; especially if the target machine doesn't have the
same version of Windows and Office.
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server
"Earl.AKA J.Alladien in access forum!!"
<EarlAKAJAlladieninaccessforum(a)discussions.microsoft.com> wrote in message
> Hi Sylvain,
> First of all I'd like to thank you for helping me ofcourse,
> And after performing the "dummy" procedure it now works, so thanks a lot
> Thanks again for your wisdom and advise!
> "Sylvain Lafontaine" wrote:
>> "Earl.AKA J.Alladien in access forum!!"
>> <EarlAKAJAlladieninaccessforum(a)discussions.microsoft.com> wrote in
>> > Hi Sylvain,
>> > Just so you know I did install the EDI framework, and the DB I
>> > downloaded
>> > comes in 2 files one that generates from ACCESS to an EDI, and one that
>> > translates an EDI into ACCESS, the last one works fine,...al references
>> > are
>> > also set,so there is no problem there!
>> First, you should have given this information in the first place.
>> You should also explain if in the second file, the � Set oEdiDoc =
>> CreateObject("Fredi.ediDocument") � is working properly or if they isn't
>> of them.
>> If you are in the situation where the instruction � Set oEdiDoc =
>> CreateObject("Fredi.ediDocument") � works in one file but not in another,
>> then maybe the second file is corrupted or is partially wrongly compiled
>> the references are not set correctly.
>> The first thing to do would be to fully decompile the faulty file and
>> launch a full compilation from the Debug menu:
>> 1- Open the References window from the VBA editor.
>> 2- Add a dummy reference.
>> 3- Close the References windows (Important!)
>> 4- Reopen the References windows and remove the dummy reference
>> Now that the references has changed, Access will flag all modules as
>> of need to be recompiled. Launch the Recompile All Modules from the
>> menu of the VBA editor.
>> Alternatively, create a windows shortcut with the following startup
>> /decompile /compact /repair
>> Another thing to try would be to use late binding instead of early
>> replace the instruction � Dim oEdiDoc As Fredi.ediDocument � with � Dim
>> oEdiDoc As Object � or maybe even simply as a variant: � Dim oEdiDoc �
>> Sylvain Lafontaine, ing.
>> MVP - Windows Live Platform
>> Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
>> Independent consultant and remote programming for Access and SQL-Server