craigkrum
16-Jun-2010, 11:45 AM
It's been pretty quiet, so I thought I'd check back on this issue. Using the Check Database function to add new fields only works the first time. Using it again to add additional fields does not map them correctly. It will include the names of the new fields, but not the actual links to the database elements, and you can not manually map the fields to the correct ones. Again, a quick way to demonstrate this is:
Step 1: Create a database with 1 field in it (any name, any type, any size)
Step 2: Create a report on this database that displays the one field.
Step 3: Add a field to the database (any name, any type, any size)
Step 4: Use check database to add the new field to the report. (Appears in bold and maps to the correct database element)
Step 5: Add another field to the database (any name, any type, any size)
Step 6: Use check database to try and add the new field to the report. (Does not appear in bold, and does not map to the correct database element.)
I've pretty much decided I have to start my report over to get the correct field mappings, but my application is in the development stage and I am sure I will run into this problem again as new fields get added.
I seem to be the only one who has run into this situation, but if someone else could try this out and let me know if it does or doesn't work for them, I would really appreciate it. As I recall, the Check Database feature was pretty important to everyone.
Thanks,
Craig
Step 1: Create a database with 1 field in it (any name, any type, any size)
Step 2: Create a report on this database that displays the one field.
Step 3: Add a field to the database (any name, any type, any size)
Step 4: Use check database to add the new field to the report. (Appears in bold and maps to the correct database element)
Step 5: Add another field to the database (any name, any type, any size)
Step 6: Use check database to try and add the new field to the report. (Does not appear in bold, and does not map to the correct database element.)
I've pretty much decided I have to start my report over to get the correct field mappings, but my application is in the development stage and I am sure I will run into this problem again as new fields get added.
I seem to be the only one who has run into this situation, but if someone else could try this out and let me know if it does or doesn't work for them, I would really appreciate it. As I recall, the Check Database feature was pretty important to everyone.
Thanks,
Craig