Sorry about the direct reply. Something is wrong with the settings. I'll try changing the posting settings.
But I meant the Cust, not the CustPO.
Bill
----- Original Message -----
From: "dnwinberry" <winberry.doyce@roadsysinc.com>
To: "MS Access Professionals" <MS_Access_Professionals@yahoogroups.com>
Sent: Tuesday, August 27, 2013 2:49:10 PM
Subject: [MS_AccessPros] Re: Error 3163 when customer number is 01246
Bill,
Your reply:
"Doyce
The error is telling you that rstInvoiceHeader!CustPO is too small. Open up the table in design view and check its size.
Bill
PS: hope this goes through this time."
came my email. However, the CustPONo is text and 30 characters. My PO Number was only 10 characters. I think it has something to do with the Customer number but I'll work on it more tomorrow. I guess I can comment out the CustPONo and try it though.
Thanks,
Doyce
--- In MS_Access_Professionals@yahoogroups.com , "dnwinberry" <winberry.doyce@...> wrote:
>
> Hey friends,
> I have a procedure that updates some records in a table it runs fine if the customer number from a combo box is "CNF" but if it is like "01246" I get Error 3163 (the field is too small to accept the amount of data you attempted to add.) The field type is text. Here is the code:
> 'Open Manual Invoice Header Table and add record
> 'Dim strMessage As String
> Dim dbsManualInvoiceHeader As Database
> Dim rstInvoiceHeader As DAO.Recordset
> Set dbsManualInvoiceHeader = CurrentDb
> Set rstInvoiceHeader = dbsManualInvoiceHeader.OpenRecordset("Manual_Invoice_Header")
> rstInvoiceHeader.AddNew
> rstInvoiceHeader!Invoice = Me.txtInvoiceNo
> rstInvoiceHeader!Cust = Me.cboCust
> rstInvoiceHeader![Invoice Date] = Date
> rstInvoiceHeader!CustPO = Me.txtCustPO
> rstInvoiceHeader!Terms = "01"
> rstInvoiceHeader!ShipTo1 = Me.txtCustName
> rstInvoiceHeader.Update
>
> What can I do to make it accept customer 01246?
>
> Doyce
>
[Non-text portions of this message have been removed]
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
Tidak ada komentar:
Posting Komentar