Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 142313 - Last Review: September 30, 2003 - Revision: 3.1
FIX: Using RI Builder & Long Table Names Makes Triggers Fail
This article was previously published under Q142313
Using the RI Builder's code along with tables that have long table names
and Private datasessions results in triggers constantly failing. The
underlying error causing the triggers to fail is Error 1 "File <file_name>
does not exist."
There are two causes. First the SET DATABASE command is scoped to Private
Datasessions. Thus, there is no Database current and the appropriate
database must be current for Visual FoxPro to be able to resolve long table
names. Second, the Referential Integrity (RI) Builder does not take this
previous issue into account.
Modify the RIOPEN procedure the RI Builder created. The modifications would
consist of finding the Database the table with the long table name belongs
to, using CURSORGETPROP(), SET DATABASE to this Database. Let the RIOPEN
routine open the table. Then use SET DATABASE to set the database back to
the original database if any.
Example Workaround
To work around this problem, make the following modifications to the RIOPEN
Procedure:
- Copy the entire RIOPEN procedure, and paste it below the "__RI_FOOTER"
- Add the following variables to the copied RIOPEN's LOCAL declarations:
- Insert the following lines immediately after the copied RIOPEN's LOCAL
declarations:
&& Replace any spaces in Long Table name with "_".
&& because this is what VFP does in the DE, Aliases
&& are not allowed to contain spaces.
__tcOldTable=tcTable
tcTable=STRTRAN(ALLTRIM(tcTable)," ","_")
&& Find the DBC name the Table belongs to
__lcCurDBC=SET('DATABASE') &&Get any current DBC
__lcDBCName=CURSORGETPROP('DATABASE',tcTable) && Get Database Name
__lcDBCName=substr(__lcDBCName,rat('\',__lcDBCName)+1) &&Remove path
__lcDBCName=substr(__lcDBCName,1,rat('.',__lcDBCName)-1) &&Remove '.DBC'
SET DATABASE TO (__lcDBCName)
&& Restore original value, the USE needs the actual Long Table name
tcTable=__tcOldTable
- Insert the following line immediately after the first ENDIF of the
copied RIOPEN procedure:
&& Set back to original DBC
SET DATABASE TO &__lcCurDBC
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. This problem has been fixed in
Visual FoxPro 5.0 for Windows.
Steps to Reproduce Problem
- Create a new database with a Parent Child Persistent Relation, and give
the parent table a long table name.
- Set the RI Builder so that there is RESTRICT on the Child table's
Insert.
- Create a new form, and add both tables to its Data Environment.
- Set the Child Cursors's BuffermodeOverride property to 5.
- Set the form's DataSession property to 2-Private Datasession.
- Add the child table's Foreign Key to the Form.
- Add a Command button to the form. Set its Caption property to Add, and
Add the following code to its Click event:
SELECT <child table>
APPEND BLANK
THISFORM.REFRESH
- Add another Command button to the form. Set its caption property to
Save, and add the following code to its Click event:
SELECT<child table>
IF .NOT. TABLEUPDATE(.T.,.T.)
=TABLEREVERT(.T.) &&Revert the change
IF TYPE('gaErrors[1,1]') <> 'L'
=MESSAGEBOX('Trigger Failed - '+gaErrors[1,2],0,;
'Data Entry Error/Trigger Failed')
ENDIF
GO TOP
ENDIF
THISFORM.REFRESH
- Run the form. Click the Add button, and type in a value that is not in
the Parent's Primary Key. Click the "Save" button.
APPLIES TO
- Microsoft Visual FoxPro 3.0 Standard Edition
- Microsoft Visual FoxPro 3.0b Standard Edition
| kbbug kbfix kbvfp500fix KB142313 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please