Results 1 to 8 of 8
  1. #1
    2 Star Lounger
    Join Date
    Aug 2001
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Dialog size - Forms (Access 2000)

    Is there a way to control the size of items like record selectors in forms, regardless of the screen settings of the user? One of my users has his screen set to microscopic and is complaining that he can not navigate through the records.
    I know what my first answer was <img src=/S/sarcasm.gif border=0 alt=sarcasm width=15 height=15>, but I'm wondering if any loungers have suggestions.

    TIA

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Dialog size - Forms (Access 2000)

    You can control the size of text boxes, labels etc., but items like the standard navigation buttons and record selectors are drawn by Access, and there is no way to influence this.

    It is possible to change the user's screen resolution from your Access database, but that is something which I myself would resent as a user (in other software than games).

    In the end, it is the user's own responsibility. If he likes to have everything microscopically small, he'll have to live with the consequences <img src=/S/evilgrin.gif border=0 alt=evilgrin width=15 height=15>

  3. #3
    2 Star Lounger
    Join Date
    Aug 2001
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Dialog size - Forms (Access 2000)

    Hi - thanks for the link, I think I'll save that for the "upgrade version" <img src=/S/evilgrin.gif border=0 alt=evilgrin width=15 height=15>.

    Cheers

  4. #4
    Silver Lounger
    Join Date
    Jun 2001
    Location
    Niagara Falls, New York, USA
    Posts
    1,878
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Dialog size - Forms (Access 2000)

    <P ID="edit" class=small>(Edited by charlotte on 30-May-03 16:00. to activate link)</P>Hi ThreeCats

    Check out

    http://www.RogersAccessLibrary.com

    for a partial solution

    RecordNavigation.mdb

    This form illustrates how to exactly duplicate the actions of the default record navigation buttons including the RecordNumber Of TotalRecords feature. The important code is in the OnCurrent events of the form and each text box must have a call to UpdateOnChange in it's OnChange event . There is no special code behind the buttons at all. I use this form as the basis for most of my forms, but the code can be imported into any form as long as you match up the object names with the names in the code.

    HTH John

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Dialog size - Forms (Access 2000)

    On that same site under Other Developers, you'll find one of my demos called "NoTables". It uses ADO, but the unbound form has simulated navigation buttons and I have built similar kinds of buttons on bound forms when I didn't want to use the built in navigation buttons. You can also use the command button wizard to create Next Record, Previous Record, etc. buttons.
    Charlotte

  6. #6
    2 Star Lounger
    Join Date
    Aug 2001
    Posts
    116
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Dialog size - Forms (Access 2000)

    Thanks Charlotte,
    And now you are rewarded for your kindness with a question. Are their advantages to using these individually generated buttons vs the Record Navigation Control (which I haven't gotten working yet)?
    TIA

  7. #7
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Dialog size - Forms (Access 2000)

    <P ID="edit" class=small>(Edited by WendellB on 02-Jun-03 11:37. Add comment about individual buttons on bound forms.)</P>I'll sub for Charlotte, and let her amplify next time she checks in.

    There are several advantages and disadvantages in using unbound forms, whether they are ADO or DAO based. The major ones IMHO are:
    <UL><LI>An unbound form lets you exercise almost total control over everything that happens in your database - for example, you can do complex and detailed error checking of data entry before you save a record.
    <LI>An unbound form doesn't save the record until you tell it to in code - bound forms often save records when the user doesn't expect it to.
    <LI>On the other hand, unbound forms frequently require lots of code - often hundreds or even thousands of lines, which translates into lots of development effort. That defeats many of the advantages of using Access as opposed to Visual Basic or other development tools.[/list]Bottom line - we use unbound forms occasionally where we want to provide Wizard-like functionallity, displaying or hiding text boxes and other controls based on previous input data, but in general we use bound controls to get the advantage of development efficiency. Now let's see what Charlotte has to say (not everyone agrees with my views on this subject).

    <font color=008080>After looking at Charlotte's post again, I realized you may have been referring to the use of individual command buttons to provide NextRecord, PreviousRecord . . . functionallity. In general they work just fine - the one challenge is to completely replicate the record counter function that you get with the standard navigation bar. I should also note that we frequently don't use the navigation bar - we may use a combo box to select records, but more often we use a TreeView. You can see a couple of samples here on our website.<font color=008080>
    Wendell

  8. #8
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Dialog size - Forms (Access 2000)

    Um ... Record Navigation Control? Are we talking about the built in navigation controls or a third part thingy? And by the way, it's perfectly possible to use buttons like those on the sample I posted with a bound form. You just use the RecordsetClone (DAO/A97 and earlier) or Recordset.Clone (ADO/A2k and later) to move to the record and then set for form's bookmark to the recordset's bookmark. The big advantage to the custom buttons is that you can make them as big as you need, you can put whatever you want in the textbox showing the count, and you can arrange them in the way that best suits your form. You don't need to use LastRecord and FirstRecord buttons unless you want, and you don't need to use an AddNew button unless you want. <img src=/S/shrug.gif border=0 alt=shrug width=39 height=15>
    Charlotte

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •