You can download CCODES01.ZIP here.
Continuous forms in Access make it possible to display and edit more than one record at a time. This is real useful, let's face it. There are, however, some frustrating limitations to continuous forms. For example, most, if not all, of the layout properties (Backcolor,Textcolor, Font, Frame etc) of the controls in the detail section of a continuous form can not be selectively set for ONE record. In another words, if you change them at all you change them for ALL instances ( all records ) displayed on the form.
So how do you flag one record? Like the active record so that the user can more easily see where cursor is. This is one of the tougher aspects of many database entry/search applications: clearly showing the user which record is active, where editing or other processes are starting from.
I have found a simple way to do this. I do not claim that this is the definitive solution to the problem (that's up to the Microssoft Corporation) but it does work and it is quite simple to implement.
CCODES01.MDB is a small (96 Kb) Access 2.0 database that demonstrates selective flagging of the active record in a continuous form. Do not expect elaborate API calls or complex Access Basic modules, cause they are not there. You'll have a good laugh when you go into the Design of the form and see how it's done, but maybe you'll find the idea useful. Like I say, it works.
A Big Thanks to The Mighty Håkan hakan.lundblad@asic.se for his input on this one. He refused to believe it couldn't be done and had a clear idea how to do it which I ruminated about and then wrote into an MDB.

Update 970321: It has been pointed out to me that the Swedish localization of Access is defective in international use. I mean that an MDB created in Swedish language Access does not translate properly when loaded in a US English Access 2.0, for example. Specifically the property EventProcedure gets stuck with the Swedish term Händelseprocedur. Access thinks that Händelseprocedur is a Macro, which it is not, and crashes out on Macro Not Found. If this happens to you (and it probably will) go into design and simply change the appropriate Event trigger name to EventProcedure. This will convince Access that there is an Access Basic Sub to execute and the demo will work. Sorry this hasn't been pointed out here earlier.

Frightening that this kind of foolishness has an unchallenged place in a mass market product like Access.

Just click HERE to download CCODES01.ZIP (20 Kb).

Unpack with PKUNZIP, open with Access and enjoy.

Click here to return to The Fortress.