It means you and Darren should get together and exchange war
stories. What version of SQL Server are you using? Any service
packs?
Basically, Many of the Emerald tables have an "IDENTITY" column, which
is a number SQL Server itself keeps. This is unique and incremented
one time for every recod inserted into that table.
For your invoices table, the identity value was set at 463, but in
actuality, highest record was 478. So the next invoice you created,
it tried to number 464, but that one already existed, and thats
what was giving the error. You should be able to create invoices fine
now.
Btw, did you have a system crash, reboot, Emerald failed something,
or ???? before this happened? I have only had like three people
report this, and can't figure out a pattern or a lead of why its
happening. Just for my defense, its a SQL Server issue, not an
Emerald issue. :(
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com