Access 2010 Bug in Packaging Wizard

[Tiger955]

Hi!

I am almost sure that there is a bug in the wizard to pack a solution including dependencies.

Whenever i try to pack the solution I step throut all mandatory fields, adding of course the accdr, the AccessRuntime.exe

All my files have no Special character but still a get the error message, that the Name of a file link file may not include Special caracters such as /\:?= etc.

But I do not have added a file link at all. So I cannot create this package and I do not find other help.

What is wrong? What does this message mean when there is no such caracters except in the path to the RT.exe and the accdr.

Thanks yr. help

BTW: how can I upload an Image when I do not have an URL and the Image is on my Notebook?

Thanks
Michael

 

[CJ_London]

have you tried decompiling and compiling the code before packaging?

 

[Tiger955]

have you tried decompiling and compiling the code before packaging?

Hi CJ!

Yes I did, the accdr has been transfered to the User's PC but he is missing some dependencies (he Needs Outlook 2010 dlls and has only Outlook 2007, so I hoped to Transfer those dll via the packaging wizard)

I hope I am not wrong at all the reach my target by doing it that way.

Michael

 

[CJ_London]

have you tried late binding?

 

[Tiger955]

have you tried late binding?

Hi CJ!

No, I did not try it, but I wouldn't see any influence on the Packaging.

How should it effect the error?

I Need the referenced dlls to be compied into the package for deploying it to the users machine.

Michael

 

[Tiger955]

I think that the error was that a Folder Name had a blank in it.

But the Thing, which I needed to get with this packaging wizard I do NOT get: the referenced dlls!

I hoped to get them and I hoped that they get installed and registered on the users machine.

 

[CJ_London]

late binding uses the version on the user machine so there is no need to include in your deployment- in this case outlook 2007 so the error should go away.

There are advantages for and against late and early binding - personally I develop using early binding and once done, convert to late binding, but then I'm supporting users with a wide variety of OS and Office and sometimes they change versions without telling me!

I've no idea if there is the risk of potential damage by you installing a 2010 dll over or next to a 2007 one. I know outlook can be particularly fussy, you would be better to change your references to use an earlier Outlook dll.

 

[Tiger955]

CJ, thanks for the info.
You are right, late binding would use the dll it finds in the target machine!!

So it could be a solution, worth to try.

Thanks a lot!