Charlotte Foust
charlotte.foust at gmail.com
Sun May 13 10:07:30 CDT 2012
Maybe I"m missing something here, but why on earth don't you simply do this in code or in a query? If the data doesn't change, there's no reason to build it into the table. If the data does change, it should do so through a user interface which can contain code or macros to run a query. If the user just thinks calculated columns are the newest miracle and wants them for that reason, gently explain to him/her that just because you theoretically can do something doesn't mean you must. If that doesn't work, hit the client gently over the head with a large hammer! Charlotte Foust On Sat, May 12, 2012 at 10:46 AM, Mark Simms <marksimms at verizon.net> wrote: > It keeps getting better. I tried to change the data type from Double to > Currency. > It accepted it. When I tried to open the table again, I got an error > "Property Not Accepted". > I performed a compact and repair....and the table disappeared ! > > The reason I needed to do this is that a custom filter : [column] <> 1 > would > fail for dbDouble. I guess I could have changed the Expression and wrapped > the 3 thousand characters in Round(), but then again, maybe that wasn't > supported. > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > >