I am running Vista Ultimate 64 LLBLGen Pro version 2. Problem also exists on 2.5

When I try to create a new project using MsAccess database I get the following error:

Connection failed. Error: The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.

SQLServer databases are OK. The Access database is readable by Visual Studio.

The provider (msjetoledb40.dll) is on my system in C:\Windows\SysWOW64

I assume that this is not an LLBLGen problem, but I thought someone else may have come across it.

Version 2.5 runs fine - perfectly - on my XP machine.

Any thoughts?

Many thanks,

Richard

What's the version (file version) of the Msjet40.dll or the msjetoledb40.dll that yo have?

Please have a look at the following thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125207&SiteID=1

Walaa,

Thanks for the reply.

msjet40.dll - Version 4.00.9635.0

msjetoledb40.dll - Version 4.0.9635.0

I followed the link you suggested. It wasn't all that helpful. It seems that MsAccess is only a 32 bit app and that is why it is in SysWOW64. No problem. The difficulty seems to be that LLBLGen cannot find the dlls.

Richard

It seems that MsAccess is only a 32 bit app

I think that's the core of it.

Does that mean I can't use Access?

For new stuff it doesn't usually matter - I would rather use Firebird or SQLServer. But I have some clients with data on Access databases.

However, I should be able to build the LLBLGen files on XP and then transfer them to the Vista machine, don't you think?

The point is that I want to be able to test that an application using a MSAccess database will run on Vista.

There is also the constraint that I refuse to develop database applications without LLBLGen, I would slit my throat before I went back to the old way

Richard

However, I should be able to build the LLBLGen files on XP and then transfer them to the Vista machine, don't you think?

Would the Jet engine then work on 64bit?

I do believe the following is true: (ref: http://en.wikipedia.org/wiki/Microsoft_Jet_Database_Engine) The Jet Database Engine will remain 32-bit for the foreseeable future. Microsoft has no plans to natively support Jet under 64-bit versions of Windows. This means that native 64-bit applications (such as the 64-bit versions of SQL Server) cannot access data stored in MDB files through ODBC, OLE DB, or any other means, except through intermediate 32-bit software that acts as a proxy for the 64 bit client

There is also the constraint that I refuse to develop database applications without LLBLGen, I would slit my throat before I went back to the old way

That can make a good advertisement banner.

I don't know if you have tried all the suggestion on the previously posted link or not. Some of them suggested manully registering those dlls using regsvr32. Some suggested forcing your app to use the 32 bit .

Someone said:

The only way it will run under 64-bit Vista is from within a 32-bit application process. So essentially your application would have to be a 32-bit application which runs under the WOW64 subsystem. You cannot develop a 64-bit application that uses Jet

Here are some other links I found: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=479203&SiteID=1 http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1928864&SiteID=1

Walaa,

Thanks for all that.

I did try the regsvr32 route and it didn't work.

I will have a look at the other links when I get time tomorrow. It is getting late here so I will see what happens tomorrow. If I find a solution I will let you know.

Richard

I haven't solved this. However, I can get around it. If I run it from a Virtual PC running Win XP everything is OK. I ony have a few apps to maintain running Access and I try to steer clients away from it. So it isn't really an issue.

If anyone does know the answer to the Vista problem I would be interested to hear, but as far as this problem is concerned you can call it closed.

Many thanks,

Richard

I'm having the exact same issue with 64 bit Vista. I'm surprised there hasn't been more people having this issue. I've tried everything on the net but nothing seems to work. I guess I'm stuck running the designer in a virtual pc.

Has there been any work on this over the last year and a half?

-Keith

It's not solveable, MS hasn't released an OleDB driver for Access for 64bit, c'est la vie.

Otis wrote:

It's not solveable, MS hasn't released an OleDB driver for Access for 64bit, c'est la vie.

Heh, yeah I'm not sure I fully understand what is going with Microsoft on the lack of 64 bit drivers.

I thought 32 bit programs should be able to use the 32 bit drivers though? LLBLGen being 32bit I figure this should work.

-Keith

kkemp wrote:

Otis wrote:

It's not solveable, MS hasn't released an OleDB driver for Access for 64bit, c'est la vie.

Heh, yeah I'm not sure I fully understand what is going with Microsoft on the lack of 64 bit drivers.

I thought 32 bit programs should be able to use the 32 bit drivers though? LLBLGen being 32bit I figure this should work.

-Keith

One would think that yes, but do you indeed run it on the 32bit CLR? Or on the 64bit clr?

Otis wrote:

One would think that yes, but do you indeed run it on the 32bit CLR? Or on the 64bit clr?

I assume that since it's compiled for 32bit it uses the 32bit CLR?

-Keith

kkemp wrote:

Otis wrote:

One would think that yes, but do you indeed run it on the 32bit CLR? Or on the 64bit clr?

I assume that since it's compiled for 32bit it uses the 32bit CLR?

-Keith

I'm not sure but my guess is that you have to explicitly have to order it to run on 32 bit. (but how to do that I don't know as I never had to do that. In IIS you have to explicitly order it to run on 32bit though)

Frans: I just reread this (after my other post): what you need to do is set the build configuration platform target from Any CPU to X86 (Under Build - General section . Platform target: ). Then llbpro will be built to tarket x86 explicitely and will find its way to the 32bit jet database. Let me know... Tot ziens Theo

See other thread you posted

Otis wrote:

We won't build the code for 32bit only, as that would force 32bit on systems which are 64bit.

If you want to run the application on 32bit, force it to do so by using corflags: http://blogs.intesoft.net/post/2007/12/Running-NET-Apps-in-32-bit-mode-on-64-bit-Windows.aspx

(I searched for it once you gave the hint about the target). This should make the designer run on 32bit.

Replying with the information here just incase someone only comes across this thread.

Thanks for this link, that's an excellent work around.

-Keith

kkemp wrote:

Otis wrote:

We won't build the code for 32bit only, as that would force 32bit on systems which are 64bit.

If you want to run the application on 32bit, force it to do so by using corflags: http://blogs.intesoft.net/post/2007/12/Running-NET-Apps-in-32-bit-mode-on-64-bit-Windows.aspx

(I searched for it once you gave the hint about the target). This should make the designer run on 32bit.

Replying with the information here just incase someone only comes across this thread.

Thanks for this link, that's an excellent work around.

-Keith

Good point, will do that next time. Thanks for reposting

hiya,

Glad I found this post. The thing is, i've only got 3,5 ,net framework installed (VWD)..I can't find the corflags.exe anywhere...Does it have a different name under 3.5?

Cheers,

yogi

It (CorFlags.exe) sould be found in the one of the locations the link mentioned: Program Files\Microsoft SDKs\Windows\v6.0\Bin\x64\CorFlags.exe Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\Bin\CorFlags.exe

VWD = Visual Web Developer ?

Anyway it's a matter of your operating system. That tool is meant to force .NET to run an app in 32-bit (or 64) mode.

Also please see this post: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=95411&ThreadID=17043

It has an attachment, which is a simple program to run the designer under 32bit. Please read the post what to do with it.

hiya,

Ok, I downloaded the exe and ran in the llblGenPro install folder..exactly as advised.

I looked in taskManager, and noted that the exe does not have a "*32" at the end of it.

I get the following error:

<<32 bit runner has stopped running. A problem has caused the program to stop working correctly.Windows will close the program and notify if a solution is available.>>

I'm utterly confused. I also looked thru this post:

http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=17043&StartAtMessage=0&#95411

I only have to use the drivers for msAccess and sqlServer...So. I'm not sure how much of the Oracle info in the posts is relevant.

Can anyone advise? I'm on win7 64 bit and keen to get started.

Many thanks,

yogi

did you also copy the llblgenpro.exe.config to LLBLGenPro_x86.exe.config?

You have to run the LLBLGenPro_x86.exe exe, which is a 32bit program and which will simply execute the llblgenpro.exe application in 32bit. OleDb only works on 32bit, so if the application isn't running under 32bit, it fails.

If the LLBLGenPro_x86.exe application fails somewhere, it of course doesn't work, so first we've to fix that.

hiya,

Yes, the config files are there.

Folder: C:\Program Files (x86)\Solutions Design\LLBLGen Pro v2.6 Demo

files: 1) llblgenpro.exe.config 2) llblgenpro_x86.exe.config 3) LLBLGenPro.exe 4) LLBLGenPro_x86

I run LLBLGenPro_x86

it states, <<trying to load and run C:\Program Files (x86)\Solutions Design\LLBLGen Pro v2.6 Demo\LLBLGenPro.exe >>

Then I get the error that I cited in the previous post. Where do I go now?

Thanks,

yogi

yogiberr wrote:

hiya,

Yes, the config files are there.

Folder: C:\Program Files (x86)\Solutions Design\LLBLGen Pro v2.6 Demo

files: 1) llblgenpro.exe.config 2) llblgenpro_x86.exe.config 3) LLBLGenPro.exe 4) LLBLGenPro_x86

I run LLBLGenPro_x86

it states, <<trying to load and run C:\Program Files (x86)\Solutions Design\LLBLGen Pro v2.6 Demo\LLBLGenPro.exe >>

Then I get the error that I cited in the previous post. Where do I go now?

Thanks,

yogi

ah, it doesn't work with the demo, as that exe is obfuscated, so it can't find the method to start with. As you're a licensee (If I recall correctly), why not use it with the full 2.6 install?