-
Okay. First you'll need to set your form's programming language to VBScript. I don't remember exactly where that is in IP2003 -- in 2007, it is under Tools/Form Options/Programming. You can right click the date field your user is entering their start date, and in the context menu, under Programming, select the On After Change event. ...
-
Well, if you are using IP 2003 and are not using Visual Studio, you'll need to use JScript or VBScript. Code goes into form events, so you need to add an event to the field or action that should trigger the date calculation. Can you provide some more information about the types of date calculations you need to do?
-
Hi, and welcome!
I created a 2003 version of a template I made with some samples to get the days, months and years using rules. You can find that here.
As far as date math, in IP 2003, you'll need to use code for that. Are you using script or managed code?
-
You aren't a pain at all! Export the source files. Close the form. Change the schema file in the folder with your source files. Open manifest.xsf in your source files in design mode, and 'Save As' a new .xsn to basically 'repack' those source files up in a template..... make sense?
-
Actually, I got this to work, using your code on a blank form. I had to be sure that the URL pointed to the library I wanted to save in, so http://server/site/library worked, but http://server/site/library/forms/allitems.aspx did not. Experiment with the URL you are using as a path in the SetSaveAsDialogLocation method.... oh, and I saved to ...
-
I don't know of a way to make a field default to caps, but you can use the translate function to change a field to all caps -- so, in your rule, you could use a condition based on a formula that translates the field to all caps.
A sample form is available here showing the use of translate() for this.
-
Is rule 1 running? Throw a dialog box in there, see if it pops up....
Or show your query field on your form somewhere so you can see if it is being populated....
-
Hi, Jeff:
Is Item 1 in rule 1 an action? Or a condition? I would think it would be a condition -- you don't want action #3 to run unless item 1 is true, right?
So, Rule 1, I think, should be based on the condition that the document is not new, and have 2 actions: 1) set the query field and 2) run the query
Rule 2 should have a condition to ...
-
Well, if you have a value in the ID field (data fields), then the form is not new. You could use that for a condition -- if ID field is not blank.....
-
After you saved as source files, did you close your form? If the form is still open, it is 'using' those form files, like the schema, so they will open read only....