For now just change your default to zero in the Plum IDE. We've entered this as a bug to be fixed in the next release.
Thanks for catching this. Respectfully, Adam Phillip Churvis Member of Team Macromedia Advanced Intensive Training: * C# & ASP.NET for ColdFusion Developers * ColdFusion MX Master Class * Advanced Development with CFMX and SQL Server 2000 http://www.ColdFusionTraining.com Download CommerceBlocks V2.1 and LoRCAT from http://www.ProductivityEnhancement.com The ColdFusion MX Bible is in bookstores now! ----- Original Message ----- From: "Jeff Fleitz" <[EMAIL PROTECTED]> To: "[email protected]" <[email protected]> Sent: Monday, August 16, 2004 9:43 AM Subject: [plum] Bit Values and Access > I have an Access table with a boolean column and where the default > value is 0 (zero). > > In the IDE, that column is defined as a bit type and given a default > value of 'False'. The Checked and Unchecked values default to 1 and 0 > respectively, and when you try to move away from the column to another > column in the IDE, it triggers a validation error. Suggest you change > this behavior so that the default value matches the Unchecked value for > a bit, so that the user doesn't become confused. I have always used 1 > and 0 to default an Access Yes/No value, so if we need to change this to > 'True/False' to work with Access in Plum, then it should be documented. > > Jeff > > -- > _______________________________ > > Jeff Fleitz > Tekquest, Ltd > Integrated Digital Solutions > http://www.tekquest.com > 866.472.5868 > _______________________________ > > >
