[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 976
  • Last Modified:

Solution--IDSQL32.DLL and Access Violations

Since there seems to be alot of people having this problem I am posting the answer here so that in all our roamings we can all replay with a solution till Borland fixes this bug in their BDE.  The bug occurs and is reproducable by just setting one DefaultExpression on any DataSet.  If you do this you will get an Access Violation with IDSQL32.DLL.  

Solution:
Assign a CustomConstraint on the DataSet that you want a DefaultExpression in and this will fix the problem.  Make the CustomConstraint global for the entire DataSet and not just for the field(s) you want to set a DefaultExpression to since the local CustomConstraint for the specific field will only fix the DefaultExpression for the field alone and still give you the AV for any other DefaultExpressions.  I normally use a CustomConstraint like "FIELD IS NOT NULL" to fix the problem.

Pass this info along to all who have problems.

This ANSWER is free and will remain free here.  Someone "Answer" this question so that it will be packed and kept.

Scott
0
millerw
Asked:
millerw
1 Solution
 
julio011597Commented:
Here it is, and thanks for the infos.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now