Asger Blond
ab-mi at post3.tele.dk
Sat May 21 18:09:23 CDT 2011
Never underestimate your unconscious intervention... Asger -----Oprindelig meddelelse----- Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Arthur Fuller Sendt: 22. maj 2011 00:48 Til: Access Developers discussion and problem solving Emne: Re: [AccessD] Tabbed form problem Guess what? Somehow (without my conscious intervention) Access suddenly decided that the BE should be Read-Only, and that was the source of all my difficulties. So I copied it and renamed the old one to BE_RO and renamed the copy to <appName>BE, and lo and behold, everything worked again. I have no idea what I might have inadvertently done to cause Access to mark the BE ReadOnly, but it did, and now that I[ve sorted it out, I'm back in Productive City (i.e. billable time). A. On Mon, May 16, 2011 at 11:48 AM, Arthur Fuller <fuller.artful at gmail.com>wrote: > I understand all that, but last week it worked as is and this week it > doesn't. Nothing else has changed. I'm thinking now of rebuilding said form > from scratch and seeing if that behaves like a good little child. > > A. > > On Mon, May 16, 2011 at 11:43 AM, Charlotte Foust < > charlotte.foust at gmail.com> wrote: > >> That could be part of your problem. Loading forms/subforms JIT makes >> sense every time. It reduces the load on the CPU so the form opens >> faster. Each subform opens only when it needs to, so you don't waste >> time loading a subform the user never visits. If you exhaust all the >> other things to try without fixing the problem, JIT might do it for >> you. >> >> Charlotte Foust >> >> > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com