>I just went through updating one of my applications from 3.01 to 4.0. I have spent the better part of today trying to get around errors when I tried to enter an application after upgrading. During the upgrade I ran xxfwdata with the security option because I am very anxious to use this part of the new upgrade. However I am in desperate need to get an update out to one of my users. To make a long story short...I deleted xxusyssi,xxusysae,xxusysgx,xxusysg,xxusysac and xxri data files to remove the optional securit features and I did get into my application finally. However, I was not able to enter in a new user. I had all of the fields keyed in correctly, I had the right length on my password...basically I checked all of the trigger code and made sure everything was right. I still could not enter a user. As a last resort I ended up deleting the trigger code for the user data file. Now, I can finally enter a user.
>
>#1. Is it ok that I deleted the trigger code, keeping in mind that I do want to use the security features after I have become more familiar with how it works?
>
>#2 Am I the only one that has had this problem? Any ideas of what I am doing wrong?
>
Paul,
#1 - The trigger code you deleted has nothing to do with the security system. The tables do but the triggers don't. The trigger code is used to implement the new VMP Referential Integrity engine. As to why you are experiencing errors, I'm not sure at the moment. The RI engine does work in VMP 4.0 but the migration plan may need to be changed; I'm not sure.

#2 - You are the first I've heard about having problems with the RI engine but you are the first that I have heard from in awhile that is migrating from 3.01 to 4.X.