A2003 mde with conditional formatting

[GraeagleBill]

I have an app primarily developed in A2003 that utilizes conditional formatting on a few of its form controls. When that app runs on A2010, none of the conditional formatting is reflected. I transferred the source code to the 2010 system and none of the CF conditions were shown for the controls of concern. What's that all about?

[ssanfu]

A95 - A2003 allowed 3 conditional format options.
A2007 on allows at least 10 conditional format options (I don't recall the max CF conditions).

Since MS changed the way conditional format options are handled/formatted, you might have to reenter the conditional formatting options

[GraeagleBill]

You're telling me that if I want to make use of CF in the A2007+ runtime environments that I have to move my app development to at least A2007? Then, if I create mde files for A2003 that CF won't be reflected there?

[ssanfu]

The one time I converted an A2000 dB to A2010, the CF didn't work and I had to reenter it (and a few more issues). Maybe I messed up or there was slight corruption.

If you create a MDE in A2003, it should be OK because the runtime is encapsulated in the mde (from what little I understand about mdes); MDEs don't require Access to be installed.

But I understood, from the reading I did (long ago), that you must use the same version of Access to create an MDE/ACCDE. (ie you can't use A2003 to create an A2000 mde).
So you would need to convert the A2003 mdb to A2007 accdb, get the dB working correctly, then create the A2007 accde to have an a2007 accde.

[GraeagleBill]

I recreated the front-end mdb to an mde file with the CF set as desired. Additionally, I did a compress/repair on the back-end mdb file, both on the A2003 system. Both files are in the A2003 format. With that, I transferred both files to the A2010 system and the CF functioned as originally expected. In A2003, and later versions I believe, perform an automatic compile when an mde file is created. If there are any errors, the mde file WILL NOT be created. I have to assume at this point that the actions stated earlier in this post must have cleaned up whatever incompatibilities that might have existed. I'm a bit befuddled as to what exactly happened.

I believe one must have Access installed in the case of a split db. Oddly enough, I don't have any systems available that don't have some version of Access install to test your assertion.