Search results

  1. B

    Use Access forms as a front end to SQL Server

    jumping in late here but..... why not just use an .adp as opposed to an .mdb I use SQL2005 to backend apps across our WAN. Performance is great. I use forms with many subforms. Each subForm can be reset from the OnCurrent Event of the main form. Simply set the param for each subform from there...
  2. B

    Storing Variables for later use.

    Hi Bob, Thanks for the reply... I do not use DLookup. I use class modules that send the stored procedure name and parameters to the server. I always use the textbox on the form the submit button is on. I have used hidden forms in the past and would rather have an extra textbox on the one open...
  3. B

    Storing Variables for later use.

    One option is to have a text box on each form that is not visible and stores the username. When user click the submit button, in addtion to opening the target form, update the textbox with the username. Now you can always retrieve info from the usertable for the current user. Here is an...
  4. B

    Form's unique table property and stored procedure parameters

    I know this is an old thread but I have a solution. The access bug may not be fixed but I have found a way to get around it. Although the drop down list in the form for the Unique table property is blank, simply set the form.UniqueTable property when you open the form to the table you want to...
Back
Top Bottom