I have experienced this and found that it resulted from one of the
following:
1) Using Fetch 3.03 to FTP app files to the server. When this happens, I use
Timbuktu and everything works fine.
2) Creating two identical data sources and unwittingly changing something --
anything -- on one and not the other. When this happens, I download the
remote db, import the data into the local one, and then upload the local
working version.
3) Using FileMaker instead of a real database. I haven't found a solution
for this on T2K. However, I console myself with visions of V5 and SQL
running on Mac OS X.
Chris
> Ezra,
> Believe me, I did do that. I literally tried everything...i dunno, can't
> explain how I fixed it, I originally created a new datasource and set the
> actions in the existing taf to the new datasource. When that didn't work, I
> re-created the actions from scratch. When that didn't work, I deleted the
> datasource and created a new one, then set the actions to the new
> datasource. When that didn't work, I changed the fields in the action from
> layout_0 to Layout_#1. When that didn't work, I pleaded to the list...and
> tried, in no particular order, all the above over and over until finally I
> got it working.
>
> Definition of insanity:
> Doing the same thing over and over, but expecting a different result each
> time.
>
> On 10/7/02 3:52 PM, "ezra" <[EMAIL PROTECTED]> wrote:
>
>>
>> I was just about to reply to your previous post and saw this. Next
>> time it happens, just select your search actions and choose "Set
>> Datasource" from the Datasource menu and set your datasources that
>> way, again. It use to happen to me all the time and that was my of
>> fixing it.
>>
>> thanks,
>> Ezra
>>
>>
>>> Problem solved. I deleted the datasource and recreated it one more time.
>>> This time is worked. Oh, I also rubbed oil on my scalp, hopped on one foot,
>>> burned some sage, and held my breath...
>>>
>>> This kind of crap really, really annoys me. Something was corrupt in the
>>> taf, and it took x number of times doing the same thing to remove the
>>> corruption?
>>>
>>> I really need to upgrade! this old code is flaky!
>>>
>>> Thx for your help and patience.
>>>
>>>
>>> and On 10/7/02 1:25 PM, "Tom Carr" <[EMAIL PROTECTED]> wrote:
>>>
>>>> John,
>>>> Thx for your ideas. I checked the search action and theI haven't changed
>>>> anything in the db. The same app/db works fine on the test server, but
>>>> refuses to work on the deployment server. Since these are on different
>>>> networks, I have to use different datasources, but otherwise they are the
>>>> same.
>>>>
>>>> I'll keep at it. I have trashed the datasourse, remade it, remade the
>>>> search
>>>> action 10 times or more. Don't know what else to try.
>>>>
>>>> Does the tango cache get cleared when the server is restarted? (Plug-in
>>>> running with web star) thinking that maybe it is a cache thing out of
>>>> desperation.
>>>>
>>>> With fmp? Should I be using "Layout_0" or "Layout_#1"?
>>>>
>>>>
>>>>
>>>>
>>>> On 10/7/02 11:42 AM, "John Schroeder" <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> Tom,
>>>>>
>>>>> Did you change the name of any fields in FMP file "after" you uploaded
>>>>> the TAF to the server?
>>>>>
>>>>> This can cause the "Object not found" error.
>>>>>
>>>>> John
>>>>>
>>>>> On Monday, October 7, 2002, at 08:12 AM, Tom Carr wrote:
>>>>>
>>>>>> Can anyone help me figure out what this error means?
>>>>>>
>>>>>> I created a new fmp database. Then created a new datasource in T2000. In
>>>>>> tango, I am able to see the datasource and the fields without a problem.
>>>>>> But, when I try to hit the taf (search action) via a browser, I get the
>>>>>> following error.
>>>>>>
>>>>>>> Error
>>>>>>> An error occurred while processing your request:
>>>>>>>
>>>>>>> File: FBNR_Subscribers_new.taf
>>>>>>> Position: Search
>>>>>>> Class: External
>>>>>>> Main Error Number: -1728
>>>>>>>
>>>>>>> Object not found.
>>>>>>>
>>>>>>> File: FBNR_Subscribers_new.taf
>>>>>>> Position: Search
>>>>>>> Class: Internal
>>>>>>> Main Error Number: -101
>>>>>>>
>>>>>>> General error during data source operation.
>>>>>>
>>>>>> I have other taf's and fmp database's on these two servers that work
>>>>>> properly. I have tried to work this out for several days now and cannot
>>>>>> get
>>>>>> anywhere.
>>>>>>
>>>>>> Your help is greatly appreciated.
>>>>>> Thx!
>>>>>>
>>>>>> --> [groundZER�]
>>>>>> --> [t:o:m:c:a:r:r]
>>>>>> --> [[EMAIL PROTECTED]]
>>>>>> --> [847:757:4188]
>>>>>>
>>>>>> ________________________________________________________________________
>>>>>> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>>>>>> with unsubscribe witango-talk in the message body
>>>>>>
>>>>>
>>>>> ________________________________________________________________________
>>>>> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>>>>> with unsubscribe witango-talk in the message body
>>>>
>>>>
>>>> --> [groundZER�]
>>>> --> [t:o:m:c:a:r:r]
>>>> --> [[EMAIL PROTECTED]]
>>>> --> [847:757:4188]
>>>>
>>>>
>>>> ________________________________________________________________________
>>>> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>>>> with unsubscribe witango-talk in the message body
>>>
>>>
>>> --> [groundZER�]
>>> --> [t:o:m:c:a:r:r]
>>> --> [[EMAIL PROTECTED]]
>>> --> [847:757:4188]
>>>
>>>
>>> ________________________________________________________________________
>>> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>>> with unsubscribe witango-talk in the message body
>>
>> ________________________________________________________________________
>> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>> with unsubscribe witango-talk in the message body
>
> --> [groundZER�]
> --> [t:o:m:c:a:r:r]
> --> [[EMAIL PROTECTED]]
> --> [847:757:4188]
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
