Now *here's* an odd problem with dclerk

[Jay R. Ashworth]

On Mon, Mar 17, 2008 at 06:45:10PM -0400, Bruce Easton wrote:
> Jay - not sure what you mean by confirmed using dscreen and dclerk,
> specifically the reference to dscreen.   Maybe you are saying you've
> confirmed with a real field indicator on a screen and not just the
> browse that the field is populated with 'N'?


I mean the screen says (in dclerk) that the field contains N, and I
checked that screen with dscreen to make sure that's really field 44.

> I hate to get nit-pickety, but ... the field that holds 'N' is
> one byte, right?

1,allup, yes.

> And yes, thinking about Jeff's question, depending on the unexpected
> behavior you are experiencing with browse vs. screen (if that's what appears
> odd), an auto table could be involved.  Easy enough to test -
> running without the auto table.

And indeed, that solved it.  Now to figure out *how* it's breaking it.

Again: filePro being unhappy with internal stuff and bailing instead of
giving useful error messages.

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274

	     Those who cast the vote decide nothing.
	     Those who count the vote decide everything.
	       -- (Joseph Stalin)