• WSClausParkhoi

    WSClausParkhoi

    @wsclausparkhoi

    Viewing 15 replies - 31 through 45 (of 86 total)
    Author
    Replies
    • in reply to: Display Digital Clock in a form (97 SR1) #566967

      Well, we made our replies concurrently.

      To make the proposed code sequence work as I imagine you would like it to, reset the timer interval in the timer event, e.g.:
      Me.TimerInterval = 400 ‘ (or whatever timerinterval you need)

    • in reply to: Display Digital Clock in a form (97 SR1) #566960

      A combination of a textbox and a timer event for the form will do it.
      Define a textbox to hold the time.
      Use a timer event to update the time in the textbox repeatedly using your preferred timer interval.
      You will find help about timer events in Access help.

    • in reply to: append query (version 2000) #566953

      We need additional information. Please explain:

      1. Tell in plain words what your aim is (e.g. I want to add a new client to a table of clients)
      2. Describe the tables involved – primary keys and other major fields
      3. How are they joined?
      4. You say “append…… just the items I selected”. Is it about records on a subform or a filtered main form?
      5. Show your append query
    • in reply to: Not In List and After Insert (2000) #566935

      Darsha,

      From your description I read that tblClients has two fields only: ClientID and ClientName. I assume that ClientID is an autonumber.
      If true, replace the code from DoCmd.OpenForm through End If (before Case vbNo) with this:

      Dim dbs as Database
      Dim rst as RecordSet
      Set dbs=CurrentDb
      Set rst=dbs.OpenRecordset(“tblClientList”)
      rst.AddNew
      rst!ClientName=NewData
      rst.Update
      rst.close
      Response=acDataErrAdded

    • in reply to: Not In List and After Insert (2000) #566926

      Darsha,
      The cause of all your trouble is that your code never gets to process the requery of the combobox. The way the NotInList event is coded the Response = acDataErrAdded stmt is never executed, since your frmClient will never be loaded at the point in your code where you check for it

    • in reply to: #name on report (97-2) #566231

      I’ll bet you close your form in your button click event just after opening the report. Then the reference to the date on your form will be invalid once you get to page 2 on your report.

    • in reply to: How to modify a query #566212

      If you have to do it in VBA I suggest you consider using DoCmd.RunSQL.
      Then you are free to compose your SQL stmt as you wish incl. the construction of the WHERE clause you need for your job.

    • in reply to: How to modify a query #566201

      Arage,
      Is this a continuation of your post on numerous entries in a textbox? I.e. is what you are asking really how to deal with that in a WHERE clause?

    • in reply to: Moving to Access2002 (A2k and A2K+2) #566120

      Wendell,

      You may have a look at Woody’s Office Watch Vol. 7 no. 3 and no. 4 if you haven’t already been there.

    • in reply to: How to modify a query #565962

      Arage,
      If you want to use a value in a control on your form as a criteria in a stored query you very often don

    • in reply to: NotInList event / add new record in a subform (97/SR-2) #565884

      Stephan,
      If you would like to, you can do the
      Docmd.GotoControl “subformname” and the
      DoCmd.GoToRecord acActiveDataObject, , acNewRec
      in your code replacing the call to the macro.

    • in reply to: FLAT FORM vs. SUBFORMS (2000) #565862

      When you create a referential one-to-may relation between Customers and Orders on CustomerID (which is a sensible choice) you are telling the system, that a customer must exist (i.e. stored in the Customers table) in the database before placing an order for that customer.
      You CAN have a flat form for the order entry even without a query as long as you make sure that either 1) you select an existing customer for the order or 2) you have a mechanism to detect that the customer does not exist and then create and store the new customer to the Customers table before saving the new order.
      An effective way of doing/ensuring this is to use a combobox (bound column = CustomerID) for the customer selection on the order entry form. You must have a NotInList event for the combobox, if you want to enter a new customer via the form. Code in the NotInList event will have to make the end user choose whether to accept or cancel when the customer name typed in the combobox does not already exist in the Customers table. In the case of accept you will have to create and store the new customer entry in the Customers table. Personnaly I prefer to let the NotInList event open a customer entry form using addnew and dialog mode.
      You can find help for the NotInList event in Access help and I think you should also take a good look at the Nothwind sample application (in particular the Orders mdb) on your Office CD.

    • in reply to: Find/Replace # sign (97) #565715

      If this is a one time event and you want to get rid of all occurences of # in your table or in just one column of your table, then just open your table and click the replace tool (in the Edit menu). Choose your options. Look for # and let the replacement line stay empty.

    • in reply to: Combo Box Requery (Access 2000) #565713

      Peter,
      The Activity_ID_GotFocus event for your combobox is not triggered when you close the form used for added activities to your activity table. It would be for a control on the main form.You may verify my statement by including a (Debug.Print

    • in reply to: Auto Number start point (Access 2000) #565614

      I’ll share my thoughts. Don’t use autonumbering if you want to control numbering. Using autonumbering means that you don’t care what the numbers are as long as they are unique, since that is what is needed for a primary key. Don’t show the user the autonumber on a form – it’s just an internal thing.

    Viewing 15 replies - 31 through 45 (of 86 total)