The problem you are having is really a product of bad design. You should not
use a field to store such inconsistent data, especially a field such as
Account#.
You would be better to create another field. In fact, you should probably
have another table for non-account accounts...
Steve
> Hello All,
> I have a field in my database called Account#. Despite the name, there are
[quoted text clipped - 23 lines]
> Many thanks in advance.
> Adam Kemp
F1stman - 13 Jul 2007 18:20 GMT
I am working within the constraints of an already existing system for the
department I am designing this for. For a number of reasons they need this
data to be stored in the same table. Thanks for the help.
> The problem you are having is really a product of bad design. You should not
> use a field to store such inconsistent data, especially a field such as
[quoted text clipped - 31 lines]
> > Many thanks in advance.
> > Adam Kemp