BE question
in [General]
|
From: golfinray on 22 Apr 2010 12:16 I am constantly asked to make slight changes in forms while developing. I rolled out a new form and the users want this moved and that moved or one little slight adjustment here and there or a new field added. My problem is, I can't add a new field in a BE linked table while the users are in it. I either have to catch my BE early in the morning before users get on or late in the afternoon after they are gone. Is there any way to force a save of the BE while users are in it? Thanks so much!!!! -- Milton Purdy ACCESS State of Arkansas
From: Arvin Meyer [MVP] on 22 Apr 2010 14:01 No, and you'd probably corrupt the database if there were. You can kick all the users out by using my kick em code: http://www.datastrat.com/Code/KickEmOff.txt a demo of which is here: http://www.datastrat.com/Download/KickEm.zip -- Arvin Meyer, MCP, MVP http://www.datastrat.com http://www.accessmvp.com http://www.mvps.org/access "golfinray" <golfinray(a)discussions.microsoft.com> wrote in message news:A296F17E-9231-40FC-B64D-79F285ACA1E8(a)microsoft.com... >I am constantly asked to make slight changes in forms while developing. I > rolled out a new form and the users want this moved and that moved or one > little slight adjustment here and there or a new field added. My problem > is, > I can't add a new field in a BE linked table while the users are in it. I > either have to catch my BE early in the morning before users get on or > late > in the afternoon after they are gone. Is there any way to force a save of > the > BE while users are in it? Thanks so much!!!! > -- > Milton Purdy > ACCESS > State of Arkansas
From: Jerry Whittle on 22 Apr 2010 14:13 I often add spare text (255), number (double), yes/no, and date fields to tables when developing a new database for just that reason. This works well especially when the end user is far, far away. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "golfinray" wrote: > I am constantly asked to make slight changes in forms while developing. I > rolled out a new form and the users want this moved and that moved or one > little slight adjustment here and there or a new field added. My problem is, > I can't add a new field in a BE linked table while the users are in it. I > either have to catch my BE early in the morning before users get on or late > in the afternoon after they are gone. Is there any way to force a save of the > BE while users are in it? Thanks so much!!!! > -- > Milton Purdy > ACCESS > State of Arkansas
From: Peter Hibbs on 22 Apr 2010 16:26 Milton, Perhaps this site will help with the Back-End update problem :- http://www.rogersaccesslibrary.com/forum/back-end-update-utility_topic410&SID=bfaz7a8e-2481-be76ca6c-9z7fd268-z2f86a64.html Peter Hibbs. On Thu, 22 Apr 2010 09:16:01 -0700, golfinray <golfinray(a)discussions.microsoft.com> wrote: >I am constantly asked to make slight changes in forms while developing. I >rolled out a new form and the users want this moved and that moved or one >little slight adjustment here and there or a new field added. My problem is, >I can't add a new field in a BE linked table while the users are in it. I >either have to catch my BE early in the morning before users get on or late >in the afternoon after they are gone. Is there any way to force a save of the >BE while users are in it? Thanks so much!!!!
From: John W. Vinson on 22 Apr 2010 16:45
On Thu, 22 Apr 2010 09:16:01 -0700, golfinray <golfinray(a)discussions.microsoft.com> wrote: >I am constantly asked to make slight changes in forms while developing. I >rolled out a new form and the users want this moved and that moved or one >little slight adjustment here and there or a new field added. My problem is, >I can't add a new field in a BE linked table while the users are in it. I >either have to catch my BE early in the morning before users get on or late >in the afternoon after they are gone. Is there any way to force a save of the >BE while users are in it? Thanks so much!!!! That's why it's really important to get the backend (table structures and relationships) done right *first*, ideally before any user data is entered at all. I realize this is sometimes not possible; but in general, "adding a new field" should be a rare and exceptional event, much rarer than changing the layout or structure of a form! In some cases it's even prudent to include Userfield1, Userfield2, Userfield3 in an inital table design to allow for future expansion. I try to avoid this but it's helped in the process of prototyping and finishing up the design of databases. -- John W. Vinson [MVP] |