I have an Access form linked to two SQL tables, I had to make a change to the field length/datatype of a field named notes. The form now tells me that the "text is too long to be edited" whenever I try to add data to that Notes field in my form. I went from char to nvarchar... how do I fix this?
What is the difference between "short text" and "long text"? Both seem to have 255 characters limit. I have Access 2013, and I found a solution, that you can use Memo instead of Short text. But the problem is, that there is no "memo" data type in Access 2013. So that won't work for me.
I’m working on a form on which I like to place an unbound text box to get a long amount of data. The text boxes in link to a field table having 250-field size. Now, I’d like to be able to use a text box, which will allow me to enter from 800 to 1000 characters. Is that possible in Access 2000?
I have a large spreadsheet with one column of information which is longer than what access accepts as long text. So when I convert the spreadsheet to access all the large boxes of information are shortened so that I am losing a lot of information.
I have a long text box or memo box that I would like to filter but do not know how. How to set up a filtering feature to use for these types of boxes? I have no problems with short text boxes.
I'm trying to save the contents of a text box into a memo field in a table, but after my code runs i look in the field and it is cut off after a hundred characters or so, and the last few characters are garbled. This is the code:
Code: DoCmd.RunSQL "UPDATE orderheaders SET orderheaders.Comments = [Text127] WHERE orderheaders.OrderNumber = " & GlOrderNumber & ""
I have been using Access 2013 to make a database which outputs values to PowerPoint. Everything has been working fine up to now that I'm trying to add to the presentation.
I have two tables with data in which are both brought together in a query which my VBA code relates to to output it to Powerpoint. Both tables contain data in 'long text' fields. The data from one outputs into PowerPoint textboxes without any issues regardless of the length of the data but the data from the other one is truncated to 255 characters. It definitely says it is a 'long text' field - is there any reason it would truncate the output?
I have created some queries that are joined on long text fields (80-120 characters). I can save the query in the graphic query design window. But when I reopen the window I get messages that the Joins have been deleted. I cannot find any references to this issue. Does anyone have experience or info on this?
I don't need a lecture about the use of long text fields in Query Joins. And yes I have used Search first.
I have a comment box that was just for text. I have been asked to adapt this to allow a web URL to be typed in which would then become a clickable hyperlink (like typing in a Word document). Is this possible?
I have been using Access 2013 to make a database which outputs values to PowerPoint.
I have two tables with data in which are both brought together in a query which is the recordset my VBA code relates to to output it to Powerpoint. Both tables contain data in 'long text' fields. The data from one outputs into PowerPoint textboxes without any issues regardless of the length of the data but the data from the other one is truncated to 255 characters. It definitely says it is a 'long text' field - is there any reason it would truncate the output?
I am a pretty novice user currently playing around with Access 2013 using Office 365.
I used to love the old style Memo field where people cut put in carriage returns to split up data. I am wondering if this function has been removed with this LONG TEXT FIELD or is there a way around it.
I like it because I tend to use it as a tracking field and like the newest "comments" at the top separated by a Carriage Return...
I have encountered an issue when I was inserting a string (with newlines about 176 characters) into access table. This field in access has the data type TEXT and it was truncated after the insertion. It is strange because I have three other fields with the same format and no truncation at all. May I know what could be the reason and how/what is the recommend data type for storing long text?
I'm having an issue where when I attempt to export data from an Access database to an excel spreadsheet using VBA it truncates any field longer than 255 characters to the 255 limit. I'm using
to export it (obviously with the table name and filepath filled in) but for some reason I cannot get it to export the entirety of the field to excel. I've been doing some digging on various forums around the internet and it seems as though it may be possible to split it into various excel cells then use automation to concatenate the cells. But considering this field I am trying to get not truncated can be up to 40,000 characters theoretically, it doesn't make sense to do it that way.Do you need more information from me? I'm somewhat new to both Access and VBA.
I am at a loss as to why this error has suddenly appeared. I have a form (frmPurchaseOrders) plus a sub form (frmPurchaseOrderDetails). The sub has a combo ProdcutID row source: SELECT DISTINCT [ProductID], [ProductName], [Discontinued] FROM tblProducts WHERE SupplierID=Forms!frmPurchaseOrders!SupplierID ORDER BY [ProductName];
Column Count = 3 Bound Column = 1
If I select a Product from the combo I get error:
'Control can't be edited, its bound to autonumber field ProductID'???
I can't recall changing anything??
Why am I getting this error? I have existing orders with order details (thus proving it worked once!!).
I combined two textboxes column into a calcualted one. It is the combination of "First Name" and "Last Name" = "Full Name".I listed a calculated textbox ("Full Name") on my form. Are there anyways to edit it on the form through the "FullNameTextBox"?
The question is in the title... How do I allow people to enter data into a field once, but then lock it or disable it from being editted later. Tried this: Private Sub SubmittedD_Enter() If SubmittedD = Null Then SubmittedD.Locked = False Else SubmittedD.Locked = True End If End Sub but the If statement isn't working... it just does the Else statement regardless of wether SubmittedD is null or not.
I have a database, originally made in earlier version of Access, recently converted into Access 2010. Due to the high number of tables relationship page is quite crowded. My problem is that I can't move the page to the most left-upper corner of the relationwhip page where I still have relations but they simply can't be seen and edited; I can't move the page any further with the silpers.
I have a database / form with a hidden timestamp field [LastEdit] that is filled automatically with the current time Now() when updated. The purpose is that each time the form is opened I want it to "Goto" the last edited record.
I *think* I get around the find edit quotes because the smaller snippets below do work.
But the whole thing fails when I put it into one command as either one of these DoCmd.FindRecord DMax("[LastEdit]", "esn"), , , acSearchAll or DoCmd.FindRecord findit, , , acSearchAll perhaps because of the quotes around the variable.
I have a problem that should have an easy solution. But I can't find it.
I need to have a user add a new record. (Created a form with the fields on it, No problem , so far.)
The problem is when the user is adding a new record if they hit the PAGE DOWN Key or the mouse scroll, they then go to a new NEW record. (And if they are not paying attention they now have two new records)
I have a form where a user can change the scheduled start date for a job. On a sub form on the same screen is a list of notes relating to that job.
Any notes added, automatically have todays date and are locked when the user clicks off.
When the scheduled start date is changed I need a note to be made. Either forced, then entered by the user or automatically.
I was thinking of making the scheduled start appear in a small form and the button to make it come up could add a new note on the click event (possibly in a message).
Or even better (probably harder) any time the value is changed in the form a new note is added.
Other options could be a pop up form to add one note on a change.
I have a continious form where each record can be edited. After editing a record the form does a me.save and a me.requery (is important). After this it jumps back to the first record (seems logical), but how can I write a code that he goes back to the 'previous edited record'.
Having a problem when saving a record that has been edited and contains a duplicate field. Here is what I'm doing.
I have an existing record that is being viewed by the user. I have an edit button on the form that is displaying the record. When the user clicks the edit button I do the following
'User clicked on edit customer record
Private Sub CustEditRec_Click()
'Store current customer key in string so we can cross
'Set customer record test string so we can determine
'what the user is doing
CustomerRecStat = "edit"
' Go unlock the customer data fields for editing
UnlockCustomerFields
TxtCompanyName.SetFocus
'Go Unlock the customer editing buttons
UnLockCustomerAddButtons
'Lock the add, delete, edit buttons
CustAddRec.Enabled = False
CustEditRec.Enabled = False
CustDelRec.Enabled = False
'Go Disable the customer navagation buttons
DisableCustomerNavigation
txtCustomerKey.Visible = True
txtCustomerKey.Locked = False
txtCustomerKey.Enabled = True
'Set focus on the customer key
txtCustomerKey.SetFocus
'disable & hide the customer key combobox
cmboCustomerKey.Locked = True
cmboCustomerKey.Enabled = False
cmboCustomerKey.Visible = False
Exit_CustEditRec_Click:
Exit Sub
Err_CustEditRec_Click:
MsgBox Err.Description
Resume Exit_CustEditRec_Click
End Sub
The field which duplicate entries are not allowed in the table is txtCustomerKey. Now remember we are just editing a record NOT ADDING A NEW ONE.
When the user finished making the changes to the record we use the same procedure to save the changes as we when the user is adding a new record...here it is.
'User clicked save customer record
Private Sub CustSaveRec_Click()
On Error GoTo Err_CustSaveRec_Click
SaveCustomerRecord:
'Update the table data fields with the data contained on the form
'*** IF WE GOT THIS FAR WITH OUT ERRORS WE SAVED THE RECORD
'*** GO AHEAD & DISABLE THE FORMS VARIOUS FIELDS
'*** & BUTTONS ONCE AGAIN AS WE ARE JUST BACK TO VIEWING
'*** THE CUSTOMERS DATABASE
'Enable and unlock the customer key field
txtCustomerKey.Visible = True
txtCustomerKey.Locked = False
txtCustomerKey.Enabled = True
'Hide & disable the customer keycombo box
cmboCustomerKey.Locked = True
cmboCustomerKey.Enabled = False
cmboCustomerKey.Visible = False
'Set focus on the customer key field
txtCustomerKey.SetFocus
'Lock the customer fields
LockCustomerFields
'Enable the navigation buttons
EnableCustomerNavigation
'Lock the customer adding buttons
LockCustomerAddButtons
'Clear the record testing status
CustomerRecStat = ""
txtCustomerKey_AfterUpdate
Exit_CustSaveRec_Click:
Exit Sub
Err_CustSaveRec_Click:
'If the error generated was by a duplicate value.
'This can only be caused by the customer key as this
'is the only field which does not allow duplicate values.
'so warn the user of this duplicate value error and set
'the focus on the customer key field
If Err.Number = 3022 Then
'if user is editing a record
If CustomerRecStat = "edit" Then
'And the entered customer key has not changed
If Me.txtCustomerKey = EditCustKey Then
'Return to saving the record as the key is
'not really a duplicate
GoTo SaveCustomerRecord
End If
End If
Select Case MsgBox("This Customer ID was already located in the database. Click OK to enter a new Customer ID or Cancel to stop adding this record?", vbExclamation + vbOKCancel + vbDefaultButton1, "Duplicate Customer ID")
Case vbOK
Me.txtCustomerKey.SetFocus
Resume Exit_CustSaveRec_Click
Case vbCancel
'Go simulate undo record click
CustUndoRec_Click
Resume Exit_CustSaveRec_Click
End Select
End If
MsgBox Err.Description
Resume Exit_CustSaveRec_Click
End Sub
The problem is when the user is editing a record. The database assumes the txtCustomerKey is a duplicate in the table. However we are not adding a new record so the duplicate error is false. Its just that the txtCustomerKey is the same as the record being edited. Its not DUPLICATED its the SAME.....
Any help anyone? Sorry for the long post but I'm a strong believer in the more information the better when trying to solve a problem....