Rocky Smolin - Beach Access Software
bchacc at san.rr.com
Tue Dec 28 00:22:23 CST 2004
Mark: "If they add 15 more to inventory table...I want 25 buttons on the selection screen. My goal is no program or coding changes for an inventory change...and avoid scrolling when they do this." I don't think you can get there. Let's take the simple case: they add 3500 beers to inventory. Do you want 2500 buttons on the screen even if you allow scrolling? Without scrolling there's only one way to do it: create the buttons on the fly and size them so they'll all fit on the screen. However, if you get enough buttons the captions or pictures won't be legible. IS there some practical limit you can set on the number of records you need reflected in buttons on the screen? Rocky ----- Original Message ----- From: "Mark A Matte" <markamatte at hotmail.com> To: <accessd at databaseadvisors.com> Sent: Monday, December 27, 2004 1:41 PM Subject: RE: [AccessD] A2k Build Form from Table > Rocky, > > Lets use the example of BEER...If a place has 10 beers listed in their > inventory...I want 10 beer buttons to show on the 'Beer Selection' Screen. > If they add 15 more to inventory table...I want 25 buttons on the > selection screen. > > My goal is no program or coding changes for an inventory change...and > avoid scrolling when they do this. > > I could build ALL buttons that would fit on the page...hide them unless > there are records in the table. It might be a little tricky if they mark > one of the selections inactive(in the table)...which in theory would cause > all of the buttons below the inactive one...to be shifted up by one > position. > > I think I can work with this though. Thanks David and Rocky. > > ...but I am still open to ANY ideas or thoughts anyone has. > > Thanks Again, > > Mark A. Matte > >>From: <dmcafee at pacbell.net> >>Reply-To: Access Developers discussion and problem >>solving<accessd at databaseadvisors.com> >>To: "Access Developers discussion and problem >>solving"<accessd at databaseadvisors.com> >>Subject: RE: [AccessD] A2k Build Form from Table >>Date: Mon, 27 Dec 2004 12:11:28 -0800 >> >>Mark, as Rocky has mentioned, this will be hard if you set a max number of >>possible buttons. I was going to do a similar task once using the >>switchboard concept, only opening it up a bit to allow ten or twelve >>choices, but I never had more than 5 minutes to spend on it >> >>Basically have a dozen (or so) "picture buttons" on the form, all hidden. >>Number them consecutively such as imj1, imj2... >> >>Open a given recordset (at form load), which a column containing the name >>of >>a function or sub to run. You can use the count to figure how many buttons >>to unhide. The OnClick event of each button will have to figure out it own >>name such as Right(Me.ActiveControl.Name,1). Now take that "button number" >>and go to the given record in the recordset and call the column's function >>using EVAL() >> >> >>HTH >>David McAfee >> >>-----Original Message----- >>From: accessd-bounces at databaseadvisors.com >>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Rocky Smolin - >>Beach Access Software >>Sent: Monday, December 27, 2004 11:39 AM >>To: Access Developers discussion and problem solving >>Subject: Re: [AccessD] A2k Build Form from Table >> >> >>Mark: >> >>Everything's perfect here. Thanks. >> >>If you don't know how many records are going to be in the table or what >>the >>maximum will be, I'm not sure how you can organize a screen which won't >>have >>scrolling. >> >>You could put 40 invisible buttons on the form and make them visible and >>change their captions depending on how many records were present in the >>table. But if they go over 40 records, you've got a problem. >> >>Maybe describe more what you're trying to do and there will be a different >>approach to solving the problem. >> >>On the other topic: IS it time for the AccessD list to try another >>abortive >>attempt at organizing a conference somewhere? >> >>Regards, >> >>Rocky Smolin >>Beach Access Software >>http://www.e-z-mrp.com >>858-259-4334 >> >> >> >> >>----- Original Message ----- >>From: "Mark A Matte" <markamatte at hotmail.com> >>To: <accessd at databaseadvisors.com> >>Sent: Monday, December 27, 2004 11:12 AM >>Subject: Re: [AccessD] A2k Build Form from Table >> >> >> > Rocky, >> > >> > On a different topic...searched the web a couple of weeks ago for some >> > access stuff and your name and picture from an Access conference came >> > up...hadn't noticed your name on the list in awhile. Hope all's well. >> > >> > Back on topic: >> > Thanks for the feedback...That was the first approach I thought >> > of...but >>I >> > was concerned about scrolling and I don't want any scrolling if there >>are >> > more choices. I used 4 and 6 as examples...but as reallity goes...I >>would >> > probably need more like 30 to 40 records in the tables for some >>instances. >> > I thought of using multiple subforms side by side ( same subform but >>with >> > different selects)...with 4 subforms, when the user configures the >> > data...they would have an option of which subform(column from there >> > perspective) the data would appear in. >> > >> > I'm basically looking for a direction...or concept as you called it. >> > Hoping someone has done something like this before...and would be >>willing >> > to share the experience/problems/tips. >> > >> > Thanks Again, >> > >> > Mark A. Matte >> >>From: "Rocky Smolin - Beach Access Software" <bchacc at san.rr.com> >> >>Reply-To: Access Developers discussion and problem >> >>solving<accessd at databaseadvisors.com> >> >>To: "Access Developers discussion and problem >> >>solving"<accessd at databaseadvisors.com> >> >>Subject: Re: [AccessD] A2k Build Form from Table >> >>Date: Mon, 27 Dec 2004 10:46:21 -0800 >> >> >> >>Mark: >> >> >> >>How about a continuous form where one of the fields is a button (not >>sure >> >>how to do this - I'm a concept guy) >> >> >> >>Rocky >> >> >> >>----- Original Message ----- From: "Mark A Matte" >><markamatte at hotmail.com> >> >>To: <accessd at databaseadvisors.com> >> >>Sent: Monday, December 27, 2004 10:12 AM >> >>Subject: [AccessD] A2k Build Form from Table >> >> >> >> >> >>>Hello All, >> >>> >> >>>I'm working on a small A2k app that needs a 'kinda dynamic' approach. >>I >> >>>want a form to be displayed with buttons ( of stuff to click on ie >> >>>text >> >>>box, piture, whatever)...but I want to buttons to be displayed >>depending >> >>>on the number of records in a table. If there are 4 records...then I >> >>>want 4 buttons...6 records then 6 buttons. Each time the form >>opens...it >> >>>may have to add or remove a button depending on the values in the >>table. >> >>> >> >>>Does anyone have any suggestions/ideas/examples of the best approach >>for >> >>>this? >> >>> >> >>>Thanks, >> >>> >> >>>Mark A. Matte >> >>> >> >>> >> >>>-- >> >>>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 >> > >> > >> > -- >> > 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 >> >>-- >>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 >