1. Never allow users to test new stuff on the only copy of your database and data.

2. Rush jobs typically take twice [or more] as long to complete as jobs that are planned, thought out and designed well. A good supervisor would understand this.

3. If something bad happened during the use of your app, it is not the users fault, it is yours. This is what beta testing is far becaause there is no way you can anticipate all the seemingly goof-ball ways a user can use your app. The best you can hope for is the user can remember the steps they took before the crash. This almost never happens.

>Hi guys
>
>
>After a night long no sleep investigation, I figured out it some genius error due to my grid... Well, I build a simple grid in the form linking another table using caseid... For which is working fine. So I decided to continue investigating, since this error occured after my supervisor, well, more like my end user (non-computer personnel, actually, know nothing about computer) have tried beta test it, well, more like an test run when the software is not even 50% ready. (Yes, she is rushing me to finish my software development cycle in 1 month... I am super stressed out and alredy re-do my database twice)... Well, I figure out is something bad she did, I don't know what, that destroyed my data integrity for my main table and the grid table, which I linked in both the dbc level and the form level. Now after a strong struggling, I decided to delete all data in both tables and re-add some test data and go through the entire add-delete-pack-add-delete-pack... cycle and software works fine.
>Now, I am facing with another difficulty, how to avoid this from happening again. What she did to trigger it, is a I DONT KNOW, so would you have any ideas?
>
>Thanx for such great help,
>
>Tom