DAO360 problems - what is the best solution

[smig]

As I asked before I have some problems with DAO360.
When I try to run a db (Access 2003) on another machines in some cases I get an error the application don't recognize some basic functions like Format().
Even though these functions has nothing to do with DAO I found that removing DAO from refernces and adding it again solve the problem

As my db will be changed to MDE setting the reference on the client machine is not an option.
Now I'm looking for the best option to solve this situation:
1. Will puting the DAO from the developing machine in the same folder of the db on the client machine cause the db to use the correct DAO?
2. If I put the correct DAO in the same folder as the db (As in 1) I guess I can re-register the DAO with the correct one, but this might cause problems with other Access applicatins.
3. using late binding as suggested here http://www.access-programmers.co.uk/forums/showthread.php?t=182200&highlight=dao360

 

[HiTechCoach]

Is it safe to assume the application is split since you are using a MDE?

Assuming a split application: Are you installing the MDE on each User's local hard drive?

I have deployed 1000's of Access 2003 MDEs and have never had any issue with DAO 3.6 on XP, Vista, or Window7 running Access 2003, 2007, or 2010. All the combinations work fine with the same Access 2003 MDE installed on the local hard drive and the back end on th server.

 

[smig]

It's not MDE yet, but it will be converted to MDE
Yes, it's split db, and each user has it's oun FE application.

What's make me real wonder is I get the errors for Functions are totaly unrelated to DAO
Also I'm not changing the DAO file. I only remove the reference and put it back to the same file.

 

[HiTechCoach]

What's make me real wonder is I get the errors for Functions are totaly unrelated to DAO

When there are issue with a miss9ing reference then all the other libraries can be effected. Tnjhis include the built in VBA functions like Left() and Trim()

It is importnt to make sure that your references are all correct.

Also I'm not changing the DAO file. I only remove the reference and put it back to the same file.

What version of DAO as you selecting?

Are you running Windows 7 with SP1?

There is a know issue with DAO in Win & SP1 not being backward compatibly with all the earlier OS's. To get around this, I make all my Access 2003 MDEs on a Windows XP machine. Usually using XP Mode (a Virtual Machine) on my Windows 7 machine.

 

[smig]

Weired thing is There are no missing refernces at all.
removing the DAO from refernces and puting it back again (the same file that was before) solve these issues.

I'm developing on XP+SP3

I suspect it's caused by differnt language systems. I'm using the English interface (With Hebrew support) and noticed it's happen on system with the Hebrew interface.
My system include the MultiUI (An add on), so I can change between Hebrew and English UI, and each user can decide what he like.
Most systems will be installed with the Hebrew interface only.

 

[HiTechCoach]

I agree t6hat the issue could be caused by differnt language systems.

 

[smig]

Any idea how to solve it ?

Can I put the DAO dll with my application and late binding it ?
Can I make it as public s I'll have to link once only and not every time I need it ?

 

[ChrisO]

Smig.

What I think you will need to do is build the smallest sample database which exhibits the problem.

Then try removing the DAO reference altogether and late bind the DAO code.
Most, if not all, DAO code can run without a DAO reference.

Keep it small to start with and, if you have problems with the late binding, post it to site.

Chris.

 

[gemma-the-husky]

smig, I recall a post referring to problems with string manipulation in Hebrew (which occurred because it is a R to L language). Was it you?

Maybe there really are issues with some functions under R to L languages

 

[smig]

smig, I recall a post referring to problems with string manipulation in Hebrew (which occurred because it is a R to L language). Was it you?

Maybe there really are issues with some functions under R to L languages

These issues where in the PDF converter by Stephan Leban.
Nothing similar to this