SQL Database Integration

Re: Access and SharePoint: JET OLE DB Issue

Navid — Tue, 26 Dec 2006 10:01:46 GMT

Yes !
U Right Patrick !
I think I should use SQL instead of Access .
Thanks a lot for your recommendations !

Re: Access and SharePoint: JET OLE DB Issue

Patrick Halstead — Tue, 26 Dec 2006 08:01:17 GMT

Hi all,
I'm terribly sorry, but we don't do anything with Access and so we have no clue about the issue in this post. We recommend SQL for all database applications and we have lots of experience and advice using SQL.
Cheers

Re: Access and SharePoint: JET OLE DB Issue

Navid — Sat, 23 Dec 2006 12:01:43 GMT

as u see I think this is a different issue. isn't it ?
So is there any one who can help me on the previous post ?

Re: Access and SharePoint: JET OLE DB Issue

Navid — Sat, 23 Dec 2006 10:00:32 GMT

Hi Patrick !
I have a same problem while I'm trying to open a form from a computer that isn't join to doamin .
somewhere I read a way to solve this problem and the writer has said that he could successfully solve it . In below I typed it :
1- Modify your Data connection
2- Click on new Source
3- choose the last one ( other/advanced )
4- click next and choose Microsoft jet 4.0 OLE DB ...
5- in the forrth tab ( ALL ) select the "System DataBase" . click "Edit value" and type the path to your workgroup security file . ( this file should be in a public folder )
6- change the other tabs as you want and type username and password of your data base .
7- click next and in the next page choose to sace your password in the file .

The writer has tested this solution and successfully solved the problem .
but i couldn't .
So u can test this way and see what will happen !!

Re: Access and SharePoint: JET OLE DB Issue

garym — Thu, 27 Jul 2006 17:00:04 GMT

Did anyone ever find a solution to this??

Thanks,
Gary

Re: Access and SharePoint: JET OLE DB Issue

Patrick Halstead — Wed, 17 Aug 2005 20:31:57 GMT

OK. I hope to get a definitive answer today, but might be tomorrow. Anyway, if you have an MS internal alias, e-mail that to me and I'll cc you on the thread.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: Access and SharePoint: JET OLE DB Issue

pmbarnes — Wed, 17 Aug 2005 13:55:13 GMT

Yes, Local Intranet. I also tried it as a Trusted site. Thanks!

Re: Access and SharePoint: JET OLE DB Issue

Patrick Halstead — Wed, 17 Aug 2005 05:59:02 GMT

Hi again. I sent e-mail to MS. The general consensus over here is that the Standalone problems you are seeing on your SharePoint site are a strange permissions issue. I'm assuming that your site is in the Local Intranet zone. Please confirm. I hope to have more info in a day or so.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: Access and SharePoint: JET OLE DB Issue

pmbarnes — Tue, 16 Aug 2005 18:17:09 GMT

Great! We can be patient. I'm just glad you're even willing to help. It is much appreciated. I hope that MS will also find some value in helping us figure this out. I don't think what we're trying to do is that out of the ordinary. It should "just work".

Re: Access and SharePoint: JET OLE DB Issue

Patrick Halstead — Tue, 16 Aug 2005 18:11:43 GMT

OK, well, time to send e-mail to MS. Please be patient. Could take a day or two.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: Access and SharePoint: JET OLE DB Issue

pmbarnes — Tue, 16 Aug 2005 17:36:44 GMT

Patrick, just a quick note to say that this is a Microsoft project. I just tried deploying the template using the standalone db on an MS internal site http://team/sites/<name>) and got the same error. So it's not just my VPC domain configuration. We're running up against a deadline so we're just going to have to jettison any use of Access at this point and go with something like 26 separate xml data docs (one for each letter of the alphabet) to break up the 4200 company records (so that performance doesn't suffer). Too bad. Access should work and would have been a better data source, I think. I still hope I can learn why Access won't work.

Re: Access and SharePoint: JET OLE DB Issue

pmbarnes — Tue, 16 Aug 2005 14:39:56 GMT

Agni,

Thanks for looking into this, but as my postings state, I tried all of this. For the standalone scenario I removed the path and used just the name of the db after adding it to the template's Resources. This is as the author explains on p. 174 of *Developing Solutions with MS InfoPath.* Then I tried the shared approach explained on p. 175. I checked the path in the manifest.xsf file after adding the shared db via the InfoPath UI. It had the proper network path.

Neither approaches work with a SharePoint form library on a domain controller. Have you tried to reproduce my problem? I could send you the database file, template, whatever you need.

Patrick

P.S. Others have been having this problem, e.g., http://groups-beta.google.com/group/microsoft.public.infopath/browse_thread/thread/89ebfe2337ddf268/6b26edf02445b506?lnk=st&q=access+%22jet+ole+db+initialization%22&rnum=6&hl=en#6b26edf02445b506

Re: Access and SharePoint: JET OLE DB Issue

Agni Jonnalagadda — Tue, 16 Aug 2005 10:42:10 GMT

Hello pmbarnes,
InfoPath throws that dialog box when it cannot connect to the DB whose path is given in the manifest.xsf. In throwing this dialog box it#%92s giving the user the option to map to DB in another location.

What we open the Standalone DB solution from sharepoint -> it is searching for the access mdb file on your desktop and that is the reason its throwing the error. So the better option when you are publishing to sharepoint is to use the Shared DB approach. The only difference in the dataconnection for Shared DB approach is change the connectionString. The “Data Source” value will change from companies.mdb to something like \\system10\e\companies.mdb which is the shared path to the mdb file.

So what I would suggest is
1. Copy the mdb file to a shared location
2. Open manifest.xsf of your standalone DB solution.
3. Change the Data source value to map to the DB in shared location
4. Publish this solution to sharepoint

This should work. Please let us know if you see any issues.

Agni
InfoPath Dev India

Re: Access and SharePoint: JET OLE DB Issue

Patrick Halstead — Tue, 16 Aug 2005 07:33:09 GMT

Hi again,
You definitely don't need to do Full Trust for username. Domain-level trust with managed code works just fine. We'll look into your access issues.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: Access and SharePoint: JET OLE DB Issue

pmbarnes — Tue, 16 Aug 2005 06:44:53 GMT

Thanks Patrick. Just thought I'd give you a little update. I issued a Code Signing cert, put it in the Current User/Personal/Certificates store, signed the form and granted Full Trust. I had high hopes when I saw that I could now read Environment.UserName, but the Access problem is still there. I tried a fully trusted form with both the standalone and share approaches.