Probably you answered on a similar question already - I cannot find.
MS SQL 2005, FW 3.5, window forms
We have two persistent objects:
1. Vouchers - a grouping of financial transactions
2. Cheques - bank cheques
For both of them we use an 'user friendly' numeration.
I.e. started with 1, within a group (the voucher numbers are unique within a financial group, the cheque numbers are unique within the bank account), and no gaps.
We implemented numeration for both of objects.
For vouchers in the insert trigger.
For cheques in the C# code.
Everything worked fine, but the accountants want to see the voucher order should really match the order of the Cheque Numbers.
I.e. this is no good:
Voucher Number Cheque Number
Cheque number chains are user editable.
The system recreates every cheque voucher when the cheque changed.
Every cheque can have 1:many vouchers associated with.
I do understand that this in not a clear Open Access issue. And the direct solution would be to implement both numerations on the client side code.
But It would be grateful if you could help me with any suggestion about how to implement this easier.
E.g. if I could change the insert statement order for vouchers?
Any other idea?