Hi Nadia,

No I'm not doing anything fancy with the array. It is the result of a SQL query which is used to populate a combo list. The reason I mentioned case is because, in my code, I reference it as aEmployees, and, in the text search I find my legit code with aEmployees and one instance of AEMPLOYEES which I beleive to be the culprit.

Time to bring out the divining rod!


>The case doesn't matter. If you know the place in the form's methods code, where you use aEmployees array, put local array aEmployees[1] statement before creating this array. Are you sure, you don't pass this array into some functions? If yes, the second line in the function code (after lparameters statement) should read external array taEmployees
>
>Also make sure, you don't use this array in report. If you do, you would have to declare it global and kill afterwards...
>
>>Hi again Nadia,
>>
>>The array is local to the event, and so I don't bother with making it a property of the form.
>>
>>My problem is that, during compile, it seems to find a reference to "AEMPLOYEES" (note case) which I cannot find when searching through the form. I do find it when browsing the SCX file as mentioned below.
>>
>>Rgds
>>
>>
>>
>>>>Hi,
>>>>
>>>>I keep getting an error in compiling which says 'Unable to find Unknown AEMPLOYEES'.
>>>>aEmployees is an array created and used in on of my forms. I've used Ctrl-F to search ALL objects on the form for code using it. The instances using it are valid and work when executed.
>>>>Windows text search narrows it down to that form.
>>>>I opened the form as a table and found a case-sensitive match to 'AEMPLOYEES' in the OBJCODE memo field of the record relating to the Form object itself.
>>>>
>>>>Any ideas how I can get rid of the error? I suspect it is a remenant of old code that I can't directly access.
>>>>
>>>>TIA
>>>
>>>How do you use this array? Can you create it as a property of form?