Dr Herbie said:spivonious said:*snip*
It's one of many improvements slated -- the system is 20+ years old and dates back to a green-screen system. It was ported to C# under massive (customer induced) time pressure so the dev team at the time (before I joined) just blasted through with a direct port without any restructuring. There are a lot of 'quirks' that have never been addressed : too much time spent implementing customer changes to spend any time restructuring -- typical catch-22 as restructuring would make the day-to-day coding faster.
Dev team? What dev team? We are a VERY small business (three people) and the company is about 6 months old so we are our own dev team, IT, and everything else...
Given my poor programming skills, I think at first the database is going to be an Access database with about 20 parts or so (speed is not an issue at the moment). My concern is setting up a numbering/naming system that will allow us to grow and eventually port the system in the near future to something more powerful. The goal is that 20 years from now we are not in your situation.
Based on your post, I get that it is easier to use letters than numbers and I see no problem with that, but they will probably be acronyms because of space constraints.
Thank you all for your feedback, it was very instructive.