InfoPath Dev

Thank you Jim. After reading over your questions a second time, and trying to figure out what you were getting at with question #5.  I found the "An Overview of DBXL Permissions" document on this site.  I read it over and figured out that the default settings during install is what was faulty.  At the time I did not have ...

Hi Jim, To answer your questions: 1) Farm configuration on a single server (called MOSS), which houses the IIS application, SQL database, and the shared service provider. 2 & 3) DBXL is installed on the same website as the Sharepoint top level site, on port 80 (http://moss) and physically on the same server. 4) Was ...

Darn it, I spoke too soon. Apparantly things are just bizarre.  Let me breakdown what is happening. When logged in as "the" AD Domain Administrator on any computer (domain\ADMINISTRATOR), the workflow does not run automatically, but submitted forms show up in library. When logged in as an AD regular domain ...

Hello Everyone, Jo-Anne's solution did indeed work! Our preliminary testing of the workflow was done on the server itself.  Which makes sense as I was sitting there doing the configuration.  However, when using a diferent machine with a different login, the workflow ran automatically as it should.  Thank you for your help ...

Hi, I followed the document's instructions to the letter and changed step 6h from Object Model to Web Service as you said to, but still the workflow is failing to start when a new item is created.  It is still only working when manually invoked. [EDIT] Your idea of having Infopath publish the template to Sharepoint instead of DBXL did ...

I've redone the SPD workflow (removed all conditions) and now it showing that new forms are starting the workflow.  But now I'm getting this error in the workflow status column of the library.  "Failed on Start (retrying)" I click on that and I can see the slightly more descriptive error ...

Hello everyone, So, after a couple days of trying, I conjured a workaround using an SPD workflow ... only to run into another DBXL set back (which I will tell you about in a second).  Basically, I created a workflow in SPD for the document library that the Qdabra DAT pointed to.  To get the promoted fields to actually show ...

That is totally OK, because I couldn't tell you the difference between a demoted property and a demented propeller.  My primary concern is finding a way to name the XML based on a value in the form itself.  DBXL currently can't do it, which is unfortunate as it does everything else smashingly well.   

When using DBXL I'm publishing to it's web service.  I do not get the edit checkbox option when publishing to a web service.  I even tried saving the XSN to publish to directly to the sharepoint library (thus getting the editable checkbox), THEN importing that template into DBXL using DAT.  The promoted fields still ...

Where is the checkbox you are talking about located (SPD, IP, or Sharepoint)?  I could not find it in IP. To clarify, in IP I promate a field.  The field value is visible as a column in the Sharepoint library, but I can't edit or delete it (I can still do lookups on it from another library though).  I open SPD and start ...