InfoPath Dev

So, I've added a rule to the cboICDMCode field. It sets the value of the my:fldICDM_Text field. It uses the current() function in the filter for the formula for the value.

Give this a try - you'll need to disable your current code on the field to verify the rule is working (if there is code on the field in this copy). Right click the link in the message header, save the file locally, right click the saved file and select design to open in design mode.

 Great thanks so much for the tip.

Works just fine !!

...This project is just beginning and I am sure to have more questions.

All the Best.

Adam

Oh, great, glad that worked for you. As an aside - if this form is not in production yet, you'll want to be sure to tidy up your main data source before it is (I can tell by the way you are naming things that this is most likely your intent, but I since I noticed it, I thought I'd remind you). It is always hard to figure out what field123 is after a few months in production when you go to make a change to the template. :)

 I agree totally.....I have learned over many years that nomenclature and naming conventions are really important !!

I am only 2 weeks into this project in between 10 gazilliion other things !! But this form will be linking to an existing AccessDB and later to SQL DB...so things need to be tidy.

So, ummmm.... I know you haven't asked for advice, here, but just in case you need some...

When you say:

JAWSURGEON:

this form will be linking to an existing AccessDB and later to SQL DB

What do you mean, exactly? Are you intending to write code in the form to submit it to your DB? Or use a web service, or some other approach? I ask in case you are unfamiliar with InfoPath and submitting to databases - with InfoPath, if you want to take advantage of the native capabilities for submitting to databases, you actually have to build your database first, then base the form off it. And I don't believe it is possible to switch from Access to SQL at a later point (without rebuilding the form) - I may be wrong about that piece, but I was concerned you may be under the misapprehension that you can build your form and just add a submit button and have it submit to a DB. If you intend to build a DB bound form, I'd recommend you start with SQL to begin with (and, in general, I'm not a fan of DB bound forms as I find the tight coupling to be frustrating at the very least and often infuriating) - SQL has a free "Express" SKU that would be enough to get you started...

So now that you asked.....I have developed a very robust Database surgical practice management system that is client/server based and has been running for about 10 years.

This (nfopath form ) is the 'medical record ' part of that app. It will be pullling most of the information in from the db; but if it submits any information back I plan on implementing that task in code.

The forms will be stored with an index pointer in the db (the index will be created in the db and pulled into the form using a parameter when the form starts..then saved using the unique record pointer....and signed to lock either all or part of the record.

You are correct that I am unfamiliar with infopath...but I appreciate the suggestions...

I will be beta testing this for a while until we smooth out the kinks ( I actually have to build a custom ActiveX control for this form ..ugh...if you do any work with custom ActiveX controls let me know !!...that is really something I don't want to do)

adam