• WSJulesG

    WSJulesG

    @wsjulesg

    Viewing 11 replies - 61 through 71 (of 71 total)
    Author
    Replies
    • in reply to: SubForm (2003) #1010873

      I don’t think you can do this all on one subform (but I’m happy to be corrected!). You could probably achieve the same effect by having two subforms side-by-side, or a subform on a subform.

    • in reply to: Turning off annoying AutoCorrect functionality (2002) #974780

      Charlotte,

      thanks. For the existing application, I’ll just have to loop through all the forms and controls to set the individual text box settings – I’ve got some code I can use for this. Sometimes, there just isn’t a shortcut!

      JulesG

    • in reply to: Turning off annoying AutoCorrect functionality (2002) #974758

      Hans,

      thanks. I can stop looking for a solution that doesn’t exist.

      JulesG

    • in reply to: Insert/Delete New Record, Renumber Old (Access 200/SR1) #920148

      Hi!
      I couldn’t download your file, our security policy won’t let me, so apologies if any of this reply is irrelevant.
      I normally manage without using AbsolutePosition – perhaps I’m a bit old fashioned. I’d ascertain what the new stepnumber would be (intStepNumber), set up a recordsource, go to the first record. If stepnumber was less than intStepNumber, ignore, otherwise increment by one. Remember to update recordsource before moving on. Finally, add a new record with the desired stepnumber. Refresh the form’s data source. Voila! (at least in my simplistic universe)
      Jules

    • in reply to: Insert/Delete New Record, Renumber Old (Access 200/SR1) #920149

      Hi!
      I couldn’t download your file, our security policy won’t let me, so apologies if any of this reply is irrelevant.
      I normally manage without using AbsolutePosition – perhaps I’m a bit old fashioned. I’d ascertain what the new stepnumber would be (intStepNumber), set up a recordsource, go to the first record. If stepnumber was less than intStepNumber, ignore, otherwise increment by one. Remember to update recordsource before moving on. Finally, add a new record with the desired stepnumber. Refresh the form’s data source. Voila! (at least in my simplistic universe)
      Jules

    • in reply to: Television viewing figures (2000) #874218

      It is very difficult to check a range against a range. You may need to take this in two chunks. For example, start by checking if start of viewing was earlier than the first part of your range, and end of viewing was any time after the start of your range. That picks up the obvious records. Then reverse the check for the records that fail the first test, for end of viewing after the end of your range, and start of viewing any time before the end of your range. It sounds logical to me (gr).

    • in reply to: Television viewing figures (2000) #874219

      It is very difficult to check a range against a range. You may need to take this in two chunks. For example, start by checking if start of viewing was earlier than the first part of your range, and end of viewing was any time after the start of your range. That picks up the obvious records. Then reverse the check for the records that fail the first test, for end of viewing after the end of your range, and start of viewing any time before the end of your range. It sounds logical to me (gr).

    • in reply to: Automate Access report to PDF (Access 2000) #754893

      We use the full version of Adobe Acrobat. When installed, this creates a new printer driver emulator. The user can then view the report in Print preview, and simply select the Adobe driver as the output device. It works really well!
      Of course, the software isn’t cheap, but it can pay for itself in time saved.

      JulesG

    • in reply to: Automate Access report to PDF (Access 2000) #754894

      We use the full version of Adobe Acrobat. When installed, this creates a new printer driver emulator. The user can then view the report in Print preview, and simply select the Adobe driver as the output device. It works really well!
      Of course, the software isn’t cheap, but it can pay for itself in time saved.

      JulesG

    • in reply to: IIF Statement (2000) #752928

      Kinaida,

      you need to say “[Code ]= “6020” Or [Code] = “6030”.

      Regards,

      JulesG

    • in reply to: IIF Statement (2000) #752929

      Kinaida,

      you need to say “[Code ]= “6020” Or [Code] = “6030”.

      Regards,

      JulesG

    Viewing 11 replies - 61 through 71 (of 71 total)