I am refactoring an older project that was created pre-Verj 5.0 where all of the fields, DB resources, table names, table columns, etc are in all uppercase and I'm renaming everything to title case so PRODUCTCOST becomes ProductCost for easier readability.
I've noticed that Verj displays a yellow error notification when renaming some fields which says "Name PRODUCTMPO already exists in a different case".
A example of this is a table resource called PRODUCTS which has a column called ProductMPO. I happen to have a DB resource (which is not tied to this particular table) which is also called ProductMPO.
This isn't a huge deal but I don't understand why Verj IO cares and displays an error when ProductMPO has a totally different context in each case. One is a table column and the other is a DB resource, 2 different meanings and uses for each.
Edit: I just ran into this issue again when trying to rename a table column to a name that matches an existing field.
2 posts • Page 1 of 1
- Ebase User
- Posts: 604
- Joined: Mon Dec 09, 2013 6:37 pm
- Posts: 1304
- Joined: Wed Sep 12, 2007 12:49 pm
I think - not totally sure - that this is because of the restrictions of the FPL programming language.
Who is online
Users browsing this forum: No registered users and 3 guests