|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Hi
Using A2003 and client machines also using the same versions
I compile on my development machine a .mde to distribute on the FE on
clients machines (3 users). One of the user's machines just will not take
the compiled .mde. I have to put a .mdb on her machine, recompile, then make
an .mde on her machine for it to work.
I have tried reinstalling Access, tried re-registering the .dll but none of
this has worked.
I have the same problem with another client as well. I would dearly like to
be able to email my clients their FE .mde with instructions but this is not
possible while I have to re-compile etc.
Does anyone have any suggestions as to how I can fix this problem?
Much appreciated.
Michelle
|
|
Probably the problem PC has a different version of one of the object
libraries to which you have a reference.
The first thing to do, if you haven't already done so, is to make sure that
you have no references that you are not using. If the problem reference is
one that you are not using, and can remove, you're home free.
Otherwise, you'll need to either ensure that the same version of the
required object library is installed and registered on the problem PC, or
possibly use late binding.
Have you established which reference is causing the problem?
--
Brendan Reynolds
"Michelle" <nospammbytwo-news[ at ]yahoo.com.au> wrote in message
news:dn627d$6n3$1[ at ]otis.netspace.net.au...
[Quoted Text] > Hi
>
> Using A2003 and client machines also using the same versions
>
> I compile on my development machine a .mde to distribute on the FE on
> clients machines (3 users). One of the user's machines just will not take
> the compiled .mde. I have to put a .mdb on her machine, recompile, then
> make an .mde on her machine for it to work.
>
> I have tried reinstalling Access, tried re-registering the .dll but none
> of this has worked.
>
> I have the same problem with another client as well. I would dearly like
> to be able to email my clients their FE .mde with instructions but this is
> not possible while I have to re-compile etc.
>
> Does anyone have any suggestions as to how I can fix this problem?
>
> Much appreciated.
>
> Michelle
>
|
|
Hi Brendan
Yes. Under the References, it is the 'Visual Basic for Applications' which
resides in the c:\program files\common files\microsoft
shared\VBA\VBA6\VBE6.dll
Since you can't actually remove this reference I have tried taking a copy of
the .dll from my development machine to the users machine and registering
it, rebooting and that has not helped.
I would appreciate any other help that you can think of.
Cheers
Michelle
"Brendan Reynolds" <brenreyn[ at ]discussions.microsoft.com> wrote in message
news:u1JOpMz%23FHA.344[ at ]TK2MSFTNGP11.phx.gbl...
[Quoted Text] > Probably the problem PC has a different version of one of the object
> libraries to which you have a reference.
>
> The first thing to do, if you haven't already done so, is to make sure
> that you have no references that you are not using. If the problem
> reference is one that you are not using, and can remove, you're home free.
>
> Otherwise, you'll need to either ensure that the same version of the
> required object library is installed and registered on the problem PC, or
> possibly use late binding.
>
> Have you established which reference is causing the problem?
>
> --
> Brendan Reynolds
>
> "Michelle" <nospammbytwo-news[ at ]yahoo.com.au> wrote in message
> news:dn627d$6n3$1[ at ]otis.netspace.net.au...
>> Hi
>>
>> Using A2003 and client machines also using the same versions
>>
>> I compile on my development machine a .mde to distribute on the FE on
>> clients machines (3 users). One of the user's machines just will not
>> take the compiled .mde. I have to put a .mdb on her machine, recompile,
>> then make an .mde on her machine for it to work.
>>
>> I have tried reinstalling Access, tried re-registering the .dll but none
>> of this has worked.
>>
>> I have the same problem with another client as well. I would dearly like
>> to be able to email my clients their FE .mde with instructions but this
>> is not possible while I have to re-compile etc.
>>
>> Does anyone have any suggestions as to how I can fix this problem?
>>
>> Much appreciated.
>>
>> Michelle
>>
>
>
|
|
You might need to install the latest service releases on the problem PCs.
I'm not sure that copying and registering just that one DLL is a good idea -
that DLL may have dependencies on specific versions of other DLLs or
resources.
--
Brendan Reynolds
"Michelle" <nospammbytwo-news[ at ]yahoo.com.au> wrote in message
news:dn7dll$l06$1[ at ]otis.netspace.net.au...
[Quoted Text] > Hi Brendan
>
> Yes. Under the References, it is the 'Visual Basic for Applications' which
> resides in the c:\program files\common files\microsoft
> shared\VBA\VBA6\VBE6.dll
>
> Since you can't actually remove this reference I have tried taking a copy
> of the .dll from my development machine to the users machine and
> registering it, rebooting and that has not helped.
>
> I would appreciate any other help that you can think of.
>
> Cheers
> Michelle
>
>
> "Brendan Reynolds" <brenreyn[ at ]discussions.microsoft.com> wrote in message
> news:u1JOpMz%23FHA.344[ at ]TK2MSFTNGP11.phx.gbl...
>> Probably the problem PC has a different version of one of the object
>> libraries to which you have a reference.
>>
>> The first thing to do, if you haven't already done so, is to make sure
>> that you have no references that you are not using. If the problem
>> reference is one that you are not using, and can remove, you're home
>> free.
>>
>> Otherwise, you'll need to either ensure that the same version of the
>> required object library is installed and registered on the problem PC, or
>> possibly use late binding.
>>
>> Have you established which reference is causing the problem?
>>
>> --
>> Brendan Reynolds
>>
>> "Michelle" <nospammbytwo-news[ at ]yahoo.com.au> wrote in message
>> news:dn627d$6n3$1[ at ]otis.netspace.net.au...
>>> Hi
>>>
>>> Using A2003 and client machines also using the same versions
>>>
>>> I compile on my development machine a .mde to distribute on the FE on
>>> clients machines (3 users). One of the user's machines just will not
>>> take the compiled .mde. I have to put a .mdb on her machine, recompile,
>>> then make an .mde on her machine for it to work.
>>>
>>> I have tried reinstalling Access, tried re-registering the .dll but none
>>> of this has worked.
>>>
>>> I have the same problem with another client as well. I would dearly
>>> like to be able to email my clients their FE .mde with instructions but
>>> this is not possible while I have to re-compile etc.
>>>
>>> Does anyone have any suggestions as to how I can fix this problem?
>>>
>>> Much appreciated.
>>>
>>> Michelle
>>>
>>
>>
>
>
|
|
Hi
I would like to re-open this discussion if anyone has any other suggestions
as to the way to fix this problem?
Many thanks
Michelle
"Michelle" <nospammbytwo-news[ at ]yahoo.com.au> wrote in message
news:dn627d$6n3$1[ at ]otis.netspace.net.au...
[Quoted Text] > Hi
>
> Using A2003 and client machines also using the same versions
>
> I compile on my development machine a .mde to distribute on the FE on
> clients machines (3 users). One of the user's machines just will not take
> the compiled .mde. I have to put a .mdb on her machine, recompile, then
> make an .mde on her machine for it to work.
>
> I have tried reinstalling Access, tried re-registering the .dll but none
> of this has worked.
>
> I have the same problem with another client as well. I would dearly like
> to be able to email my clients their FE .mde with instructions but this is
> not possible while I have to re-compile etc.
>
> Does anyone have any suggestions as to how I can fix this problem?
>
> Much appreciated.
>
> Michelle
>
|
|
|