InfoPath Dev

Patrick, Thanks a ton for the response and yes, we need to discuss DBXL after I trial it today or tomorrow. This issue was resolved late last night. Removing the data connections one at a time, there was a connection that referenced the library the forms are stored. Not on Form Load, but the connection was meant to pull in the ID field ...

Bueller?  Bueller?

Thanks for the ideas. Your DBXL tool looks to be a useful tool. Requesting download now, thanks again!

Maybe creating a view for each car and using Calendar Overlay to color code available/unavailable cars. The problem is calculated fields dont work with [Today]. That is really what you would be looking for

Has anyone resolved this? My problem is that the moved XMLs point to the latest version of the template. The latest version looks a lot different than the one created 2 years ago and blows up with schema validation errors. So we need a way to point 1-xxx to version 1 of the template and xxx-xxxx to version 2..... etc We bought the Modify ...

Resolved, Hotfix resolved my issue in seconds.   Didnt require a reboot and ran the hotfix on our front end servers.  http://support.microsoft.com/kb/2436035   

Not sure if this will help you, but what we did to band-aid this issue is make the form browser enabled (2007) but set the document library to open in the Client.   We think this is what fixed our issue.

I've added it to the Local Intranet.  Not to Trusted Sites, I'll ask the guys if this would make a difference.  I wish it was a per-machine setting, but it will most likely require a GPO change.  I'm having a hard time understanding how more people havent had this problem.   We have had this form ...

We have a SP2010 environment with 2007 browser based forms.    When someone tries opening an attachment (say a PDF) in a form in Internet Explorer, it prompts with "Message from webpage"..   harmful computer....  After clicking OK another browser opens in the background and then a prompt to Save or ...

I lied, that did not solve the problem.   The problem has something to do with Office 2010 and Office 2007.  Other users and I can use the submit button and save the form the first time, but going back in and make a change and saving only works in InfoPath 2010.   2007 spits that error.   is there a patch out ...