Search results

  1. D

    Added a field to the SQL Insert within VBA and the Insert fails now

    Did I post my VBA with the proper format ? Not sure what to enclose the code with?
  2. D

    Added a field to the SQL Insert within VBA and the Insert fails now

    No, same end of VBA on first INSERT INTO attempt
  3. D

    Added a field to the SQL Insert within VBA and the Insert fails now

    Code all worked before I tried to add this last field.
  4. D

    Added a field to the SQL Insert within VBA and the Insert fails now

    {code} Private Sub Command4_Click() On Error GoTo ErrorHandler Dim db As DAO.Database Dim rstholdings As DAO.Recordset Dim savaccount As String Dim savsymbol As String Dim savdescription As String Dim straccount As String Dim strsymbol As String Dim strBegin As String Dim strEnd As String Dim...
  5. D

    Added a field to the SQL Insert within VBA and the Insert fails now

    The insert into table field name is desc and it is loaded from the "input" table with a field named description (I know it's a reserved name now) So in the vba I refer to that source table field as [description] - but still errors out on the SQL Insert?
  6. D

    This does not bring back the corresponding Matched ROW value in Column D

    =INDEX('C:\CollectorCards\EXCEL\Cards\[55BOFOOT_Sheet1.XLS]Sheet1'!$D$1:$D$113,MATCH(B7,'C:\CollectorCards\EXCEL\Cards\[55BOFOOT_Sheet1.XLS]Sheet1'!$B$1:$B$113,0)) Looks like this is working for me.
  7. D

    This does not bring back the corresponding Matched ROW value in Column D

    I don't get an error, just don't get the correct value returned ....
  8. D

    This does not bring back the corresponding Matched ROW value in Column D

    I am trying to match a COL B row from 1st book to the COL B ROW(s) of another 2nd BOOK - and bring back to COL D OF the 1st book - THE COL D value in THE MATCHED COL D ROW of the 2nd book.
  9. D

    This does not bring back the corresponding Matched ROW value in Column D

    I think it is because I am still using version 2002 and it has to do with the order of the data in the LOOKUP'd sheet. That should not be so difficult, but I guess it is so.
  10. D

    This does not bring back the corresponding Matched ROW value in Column D

    =LOOKUP(B7,'C:\CollectorCards\EXCEL\Cards\[55BOFOOT_Sheet1.XLS]Sheet1'!$B$1:$B$113,'C:\CollectorCards\EXCEL\Cards\[55BOFOOT_Sheet1.XLS]Sheet1'!$D$1:$D$113)
  11. D

    Validation rule error should not appear ?

    Worked perfectly !!!
  12. D

    Validation rule error should not appear ?

    That makes sense but must be a slight error in that code ? It's in Red.
  13. D

    Validation rule error should not appear ?

    They are defined Date/Time with Format = short date
  14. D

    Validation rule error should not appear ?

    Validation text comes up: End Date must be greater than start date
  15. D

    Validation rule error should not appear ?

    how does the comparison of dates actually work then ??
  16. D

    Validation rule error should not appear ?

    print lastsaturday 5/16/2020 print lastfriday 12/31/9999 run time error 3316
  17. D

    Validation rule error should not appear ?

    Hello ! Both are date/time Short Date
  18. D

    Validation rule error should not appear ?

    strSQL = "insert into rates ([customer], [ratecode], [saturdaystart], [fridayend], [rate]) values (""" & [findcust] & """, 'L', " & [LastSaturday] & ", " & [LastFriday] & ", " & Me.RateperHour & ")" CurrentDb.Execute strSQL, dbFailOnError On debugging, I see that value of [LastFriday] is...
Back
Top Bottom