InfoPath Dev

Hi -- can you attach a copy of your template to a reply so we can take a look at it? You can attach a file under the Options tab....

Hello: Do your users have permissions to delete xml for that document type in DAT? Open the DBXL Admin Tool, and edit the TestForm document type. Look under the Permissions tab -- are you enforcing permissions? Do your users have the right to delete? An overveiw of DBXL permissions can be found here.

Ah, I see now. The issue is that using built in InfoPath functionality, you can't filter the target of a rule. You have several options. You can use qRules to set a filtered field's value. You can manually modify the manifest file. You can use the conditional double eval method. I suppose, also you could use code.

Can you share your template? There is a spot under the Options tab where you can attach a file. I can try publishing to one of my test SharePoint sites and see if I get the same error -- we'd at least know if it was the form the SharePoint set up....

Hooray! Glad it worked!

You'll probably need to use some string functions to split up your original query and put it back together so that you can put your WHERE clause before your ORDER BY clause. Holler if you get stuck.

You'd need to use different conditions for each rule. Start with the one with the most conditions and work your way back, I think -- so your first rule would have the condition "If Algebra is present AND Geometry is present AND Chemistry is present AND Physics is present...." and then the action would set the Total field to the ...

Hi -- I have recently worked on a form where I have fields bound for To, Cc, and Bcc, and as long as the field for To is populated, everything works as anticipated. Are you making sure To is populated?

Here's a sample at Microsoft that uses script. It wouldn't be too tricky to update to managed code. Here's a thread on this forum with some additional information that might help you.If you need more help than these resources provide, please post back!

In order to submit to Access, you'll need to base your form off the Access DB when you create it. If you go to create a new form, you'll see that basing it off a database is one of the options. Perhaps add a submit button on the form that submits to Access that is only displayed for you (you can use User Roles for this, or the userName() ...