[AccessD] Access 97 nasty behaviour of subform

Lembit Soobik lembit.dbamail at t-online.de
Sun Oct 1 11:37:59 CDT 2006


I have just tried this:
open the form, run the code, close the form
now next time it should give the error
close Access
reboot the PC
start Access
open the form
run the code __>> ERROR again

so the status of whatever causes the error every other time must be saved

Now I have tried to find out whether its the Access ot the Excel file that 
stores that.

open form and run code - get error
now I know next time it should run without error.
close form
close Access
copy the excel file to a different place
open Access
open form and run code without error.

close Access
replace the Excel file with the previously saved  one (which should be good)

open Access, open form run code _ ERROR again

so it seems to me this alternating error has nothing to do with the excel 
file

there must be something in Access that cleans up each time the error 
occurs???

Lembit

----- Original Message ----- 
From: "Lembit Soobik" <lembit.dbamail at t-online.de>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Sunday, October 01, 2006 1:01 PM
Subject: Re: [AccessD] Access 97 nasty behaviour of subform


> no, FE and BE and Excel file are on same directory even
>
> Lembit
>
> ----- Original Message ----- 
> From: "Stuart McLachlan" <stuart at lexacorp.com.pg>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Sent: Sunday, October 01, 2006 11:52 AM
> Subject: Re: [AccessD] Access 97 nasty behaviour of subform
>
>
>> On 1 Oct 2006 at 11:01, Lembit Soobik wrote:
>>
>>> thank you, Stuart,
>>> seems you are right. must be the Excel table not closing or such.
>>> and I think it is not editing the subform.
>>> Sometimes a long time delay between closing and opening the mainform 
>>> agin
>>> helps, Now I just found that in case of the error closing and then
>>> opening
>>> the form fixes it.
>>
>> Is this running over a network?
>> If so, it sounds like an "oplocks" problem.   Try disabling Oportunistic
>> Locking on the server. See http://support.microsoft.com/?kbid=296264
>>
>>
>> -- 
>> Stuart
>>
>>
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com 




More information about the AccessD mailing list