[AccessD] Database Corruption?

Dunno if this will help . . .

Sometimes unexpected values in the table being aggregated will cause the domain aggregate function to puke, so I often wrap them in an Nz() function to ensure that a valid value is returned.  Something like:

If Nz(DCount("ClaimId", "Audit Detail", Criteria), 0) = 0 Then

Might be worth a try . . .



-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of RANDALL R ANTHONY
Sent: Thursday, July 31, 2008 11:31 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Database Corruption?

A97, FE and BE

Hey everyone,
I've got another one of those bizarre problems that just cropped up.  Made some extensive changes to a db.  During some regression testing a user reported a problem that the db was getting hung up.  Stepping through the code I found this anomaly:

When the code hits this line
If DCount("ClaimId", "Audit Detail", Criteria) = 0 Then

it jumps to this public function (which is not supposed to be invoked until way down the line)
Public Function ErrorCodeList(ClaimID As String) As String

When it does this, a) it hangs up because there's a boatload of records, b) shouldn't be happening.

I finally resolved it (or so I thought) by doing the ol' /decompile switch on my frontend.  Now my test FE and BE work.  However, when I connect my clean FE to the production BE, the same thing happens.  I've created a new db and imported all the tables into a new container, no go.

Any clues would be sincerely appreciated.  Thanks!
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com