newsgroups-index (beta)

Current group: dbase.bug-reports

Database Engine Error: Operation not applicable

Database Engine Error: Operation not applicable  
Gerald Lightsey
 Re: Database Engine Error: Operation not applicable  
Marty Kay
 Re: Database Engine Error: Operation not applicable  
Gerald Lightsey
From:Gerald Lightsey
Subject:Database Engine Error: Operation not applicable
Date:Tue, 28 Dec 2004 13:27:37 -0800
This occurs in the latest version of Plus but also in dB2K.

I have several programs that output values regarding the relative
distances between members of two groups. A contrived example might be a
long list of Police Stations and an equally long list of Krispy Creme
Donut shops where the output is to determine how many of the Police
Stations have at least one Krispy Creme shop within a 5 mile radius.
The routines use spherical geometry formulas some of which came from Jay
Parsons long ago.

In many cases the exact addresses for one or both of the lists is not
provided and the Latitude and Longitude values used are those for the
centroid of the respective Zip Code obtained from a purchased Zip Code
list. These variations of the program always seem to work OK.

In some cases, however, the exact Latitude and Longitude for one or both
lists is provided and the specific code for the program is greatly
simplified. I have been running into a problem in the simplified
version where, within a Do While loop, I assign a Longitude value to a
variable to be used within the spherical geometry calculations. The
second iteration of the loop fails with the message "Database Engine
Error: Operation not applicable" at this point in the program...
theLat = target->lat
theLon = target->lon <---This is the command that fails

Target is an alias for a table containing Latitude and Longitude
coordinates for the Police Stations. Normally I have both of these
numerical fields with a width of 18 and 13 decimal places. They are not
always carried out to the full 13 decimal places. Decimal Latitudes in
North America are positive numbers whereas Decimal Longitudes in North
America are negative numbers so the variable assignment that is failing
is -75.7594080000000 where it was previously assigned -78.9926630000000.
The failure never occurs in the Latitude assignment of a positive value.

I have tried making the variable local, public, releasing it, giving it
an assignment before the real assignment and using the STORE syntax all
to no avail. What does work in the program is to assign the variable to
a custom property of _app rather than a standard memory variable.

I have tried to create a turnkey example but it does not fail.

Gerald
From:Marty Kay
Subject:Re: Database Engine Error: Operation not applicable
Date:Tue, 18 Jan 2005 12:03:26 -0500
Hi Gerald,

If you can get us a test case we can try to reproduce your problem and
maybe determine exactly why its failing.

- Marty Kay (dBI) -

> In some cases, however, the exact Latitude and Longitude for one or both
> lists is provided and the specific code for the program is greatly
> simplified. I have been running into a problem in the simplified
> version where, within a Do While loop, I assign a Longitude value to a
> variable to be used within the spherical geometry calculations. The
> second iteration of the loop fails with the message "Database Engine
> Error: Operation not applicable" at this point in the program...
> theLat = target->lat
> theLon = target->lon <---This is the command that fails
>
> Target is an alias for a table containing Latitude and Longitude
> coordinates for the Police Stations. Normally I have both of these
> numerical fields with a width of 18 and 13 decimal places. They are not
> always carried out to the full 13 decimal places. Decimal Latitudes in
> North America are positive numbers whereas Decimal Longitudes in North
> America are negative numbers so the variable assignment that is failing
> is -75.7594080000000 where it was previously assigned -78.9926630000000.
> The failure never occurs in the Latitude assignment of a positive value.
>
> I have tried making the variable local, public, releasing it, giving it
> an assignment before the real assignment and using the STORE syntax all
> to no avail. What does work in the program is to assign the variable to
> a custom property of _app rather than a standard memory variable.
>
> I have tried to create a turnkey example but it does not fail.
From:Gerald Lightsey
Subject:Re: Database Engine Error: Operation not applicable
Date:Wed, 19 Jan 2005 01:14:57 -0600
In article , mkay@dbase.com says...
> Hi Gerald,
>
> If you can get us a test case we can try to reproduce your problem and
> maybe determine exactly why its failing.
>
> - Marty Kay (dBI) -

You should have the files and instructions by now.

Gerald
   

Copyright © 2006 newsgroups-index   -   All rights reserved   -   Impressum