O$:403 ODB:141 on Mac - Win Clients problem

[Philip Potter]

Hi,
When you install ODB 154, it doesn't overwrite ODB 1.41.

Is there a correct way to uninstall ODB1.41 from a Mac?

I just sense that if I delete the folder, I'm leaving some command 
somewhere trying to restart it when the Mac reboots.

Phil.

On 10/04/2013 22:41, Philip Potter wrote:
> Yes, I tried it locally and it seemed to work just fine...
> We'll see if it improves the situation at the client site.
>
> thanks for your input.
> Phil.
>
> On 10/04/2013 18:47, Bob Fiering wrote:
>> Hi Phil,
>>
>> In one of the technotes at the download section of ODB Tiger Logic 
>> says the following:
>>
>> General Rule:
>> New servers will work with older clients, but new clients will not 
>> work with older servers.
>> For Studio 4.03 this means version 1.3 or higher.
>>
>> Bob
>>
>>
>> Op 10 apr. 2013, om 18:10 heeft Philip Potter 
>> <Phil at pgpotter.demon.co.uk> het volgende geschreven:
>>
>> Hi,
>>
>> Unfortunately, I'm not able to go on site at this time, and remote 
>> access isn't possible.
>>
>> Hence why I tried it locally, thought I'd corrected the problem, 
>> asked them to try it, and it did not improve.
>>
>> Most of my work involves SQL datasets, so I'm not so familiar with ODB.
>>
>> Bob, your suggestion of using the latest ODB...
>> I take it, that it will still work with Omnis 4.03?
>>
>> Clearly there should be some improvements from 1.41 to 1.54, you'd 
>> think?
>>
>> Phil.
>>
>> On 10/04/2013 15:36, Keith Bartlett wrote:
>>> Hi Phil
>>>
>>> Try upping the logging level, might show you why the clients are 
>>> being disconnected.
>>>
>>> Cheers
>>> Keith
>>>
>>>
>>> On 10 Apr 2013, at 13:51, Philip Potter wrote:
>>>
>>>> Hi,
>>>>
>>>> I have a client that uses ODB141 on a MAC server, from Mac and 
>>>> Windows O$4.03.
>>>>
>>>> They seem to have a problem with there windows clients, in that 
>>>> quite often they get the padlock icon appearing.
>>>>
>>>> It seems they get disconnected from ODB?
>>>>
>>>> ODBSocketTimeOut is set to 120 = 2 minutes.
>>>>
>>>> In a test environment, off site, adding a timer procedure to read a 
>>>> small record every 30 seconds seemed to help, but no change, if not 
>>>> worse, on the live system.
>>>>
>>>> Any thoughts, things to consider, as to why this may be happening, 
>>>> and any thoughts on a resolution?
>>>>
>>>> thanks in advance for any help
>>>>
>>>> regards
>>>> Phil.
>>>>
>>>> -- 
>>>>
>>>> _____________________________________________________________
>>>> Manage your list subscriptions at http://lists.omnis-dev.com
>>> Keith Bartlett
>>> Adnet Ltd - (0)1491 642133
>>> www.adnetltd.co.uk
>>>
>>>
>>> _____________________________________________________________
>>> Manage your list subscriptions at http://lists.omnis-dev.com
>>>
>

-- 

P G Potter, 11 Regency Court, Mickle Trafford, Chester, UK.

This message is confidential and intended for the use only of the person 
to whom it is addressed. If you are not the intended recipient you are 
strictly prohibited from reading, disseminating, copying, printing, 
re-transmitting or using this message or its contents in any way. 
Opinions, conclusions and other information expressed in this message 
are not given or authorised by the Company unless otherwise indicated by 
an authorised representative independent of this message. The Company 
does not accept liability for any data corruption, interception or 
amendment to any e-mail or the consequences thereof. Emails addressed to 
individuals may not necessarily be read by that person unless they are 
in the office.