Sure Mark,
Here's the SQL:
SELECT *;
FROM decision Decision;
ORDER BY Decision.decision
Not very exciting is it?
The structure of the decision is:
Structure for table: D:\DOCUME~1\CANDREW\LOCALS~1\TEMP\LADC000G.TMP
Number of data records: 5
Date of last update: 1/01/1601
Code Page: 1252
Field Field Name Type Width Dec Index Collate Nulls
1 DECISIONTEXT Character 20 No
2 DECISION Character 1 No
3 WEIGHT Integer 4 No
Interesting date of last update huh?
>Could you post the SQL code that is used to create the view? When I have this problem, it is when I have concatenated 2 or more fields or used trim functions in the field selection list. The error occurs when the first record selected has empty values for those concatenated fields. The initial view structure is based on this, so that concatenated field is not wide enough for populated fields of subsequent records, requery(), etc.
>
>
>>Hi Folks,
>>
>>I have a snippet that says (in part)
>>
if ! llViewUsed
>> use (lcDBC + "!" + lcViewName) in 0
>>endif
>>
>>This gives me a Base Tables Have Been Changed error (1542), but they haven't!
>>
>>Suspending the app at this point and attempting to USE the (remote against SQL Server) view also generates the error, but modifying the view and running it from the view designer
DOES NOT!>>
>>This error occurs with a number of the views used by the form (after about 7 have been opened), but modifying one of the views and running it from the view designer and then resuming the app means that the rest of the views load fine as well.
>>
>>Any clues would be
much appreciated.
>>
>>Cheers,
>>
>>Andrew
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.