Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Designer> Access database on Windows 7 64-bit
 

Pages: 1
Designer
Access database on Windows 7 64-bit
Page:1/1 

  Print all messages in this thread  
Poster Message
omar
User



Location:
Salmiya, Kuwait
Joined on:
15-Oct-2004 15:44:57
Posted:
569 posts
# Posted on: 10-Mar-2010 11:33:04.  
using LLBL 2.6, .NET 3.51sp1, VS2010 RC
I am trying to create an LLBL project on windows 7 64-bit for an Access database source. When I select the database driver for MS Access and then select the database file then click on <Test Connection> button, I receive the following error message

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

When I create a connection string inside visual studio's project settings, I am successfull in creating the connection string and at run-time I can retrieve and access the data from the MS Access file.

Since I want my DAL from LLBL, how can I resolve this matter?
We don't know who we are until we see what we can do  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14569 posts
# Posted on: 10-Mar-2010 11:54:01.  
MS hasn't released an OleDB driver for Access for 64bit.
So you'll have to force LLBLGen Pro Designer to run in 32bit.
Please check the following similar thread for more details: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=11316


  Top
omar
User



Location:
Salmiya, Kuwait
Joined on:
15-Oct-2004 15:44:57
Posted:
569 posts
# Posted on: 11-Mar-2010 08:21:43. Goto attachments  
Having read through the provided threads in the forum, I tried the following:

1- use the LLBL_x86.exe provided by Frans on one of the threads
http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=95411&ThreadID=17043

The exe does run in 32-bit BUT when I click on the button to select the Access MDB file, it hang s. The funny thing about this is that it is only happening with the Access driver. If I select the SQL driver it would work fine

2- using the CorFlags utility to force run the LLBL designer in 32-bit, the screen capture shows the errors I am getting.
It is basically telling me that I need to use the switch /Force because LLBL.exe is strongly signed. When I do so, I get another error telling me that using the /Force switch will invalidate the signature!!
We don't know who we are until we see what we can do  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37797 posts
# Posted on: 11-Mar-2010 14:32:57.  
If it stalls on the ms access db: do you have it open? Is the file locked by another application? Other than that, I don't know... the 32bit runner should run the designer under 32bit and thus make sure the oledb provider will work.

If you run it under 32bit on another machine, is the same mdb file readable?


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
omar
User



Location:
Salmiya, Kuwait
Joined on:
15-Oct-2004 15:44:57
Posted:
569 posts
# Posted on: 14-Mar-2010 09:03:51.  
OK.. on another windows 7 64-bit machine its working fine using the CorFlags util to force LLBL to run as 32-bit application.

Now, the last issue is concerning .NET 4.0. This application is being developed using VS2010/WPF. The generated DAL is ofcourse targeting .NET3.5.

Is there away to force the generated DAL projects to target .NET 4.0 ?? Maybe by manually changing the referenced .NET dlls in the DAL projects ??
We don't know who we are until we see what we can do  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37797 posts
# Posted on: 14-Mar-2010 10:35:03.  
I think it's possible to load the .net 3.5 projects in 2010 without a problem, only the solution file is a problem. v3 (now in beta) supports .net 4.0 btw.

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
omar
User



Location:
Salmiya, Kuwait
Joined on:
15-Oct-2004 15:44:57
Posted:
569 posts
# Posted on: 14-Mar-2010 10:56:59.  
Frans.. as I am doing this small application as a proof of concept (a real life application mind you) to adopt WPF, would you advice using the LLBL beta for this case ?
We don't know who we are until we see what we can do  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37797 posts
# Posted on: 14-Mar-2010 14:55:52.  
omar wrote:
Frans.. as I am doing this small application as a proof of concept (a real life application mind you) to adopt WPF, would you advice using the LLBL beta for this case ?

The runtime has not changed much in v3, and we don't have a known bug logged for the runtime/templates at the moment, so you shouldn't run into a problem with it. It's doable to alter v2.6 to support .net 4.0 btw. I'll dig up a thread which documents it, just a sec.

edit:
http://www.llblgen.com/TinyForum/GotoMessage.aspx?MessageID=94058&ThreadID=16785


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.