Larry,

>>I've seen this when there was no LoginHistoryTable but the view existed but that is a rare circumstance to get that environment<<
Sorry, I took a while to respond. I spent many hours to isolate the problem. I found what's causing the error but I still need to fix it.

I verified that the LoginHistoryTable existed in the path while trying to commit changes to V_LOGINHISTORYONEUSER but tableupdate() was referencing the LoginHistoryTable in my development path, which is c:\gt. If I renamed the installation directory to c:\gt, the application would work properly because it could find the base table. But why should I be limited to install my app in that exact directory? Is this similar to what happened to you? How can I fix this problem? Is this possibly a VMP or an SDT problem?

I appreciate your help.

Thanks,
Evelyn