DatabaseDuane
asked on
Appending text to table from form fails
I have a form that has some stock letters which can be customized. Letters are then printed from what is in the text box. Now I am wanting to give an email option. But to do that I need to append the letter text in the form to a table.
The problem is that it pulls the first part of the text (100 characters or so) and then truncates the rest ending with some funky symbols like:
...We know you agree that auU¨
Seems like a string length issue. Any way around this?
The problem is that it pulls the first part of the text (100 characters or so) and then truncates the rest ending with some funky symbols like:
...We know you agree that auU¨
Seems like a string length issue. Any way around this?
ASKER
OK. Here is a small sample db that shows the problem. If you open up frmLetters, you'll see the text of the letter. If you click the Button at the bottom, it shows the query results that point to that form's field -- and they are truncated. Sample.mdb
Drop the AckLetterID field in the form.
Then use dlookup in the query:
DLookUp("AckLetterText","t blLetters" ,"AckLette rID=" & forms!frmletters!ackletter ID)
Sample-3--2011-08-10.mdb
Then use dlookup in the query:
DLookUp("AckLetterText","t
Sample-3--2011-08-10.mdb
ASKER
The issue is that I to grab what is in the form because people will be editing the text when the customize the letter. The text in the form on my system is actually not linked to the table -- it is simply brought over to the form into the text box. That way the stock letter may say "Thank you for contacting us." and people can edit it to "Thanks again for stopping by." But the stock letter stays put.
One thing that comes to mind is to have the form be based on its own table for the data and it will be just the one record for that particular edit.
One thing that comes to mind is to have the form be based on its own table for the data and it will be just the one record for that particular edit.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
My guess is that anyone not familiar with your design would have a tough time figuring out what this all means, or exactly how this system is put together...
...Can you explain in detail what this all means?
Perhaps it would be clearer if you posted a sample and a full explanation...
Sample database notes:
1. Back up your database(s).
2. Combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Remove any records unless they are relevant to the issue.
5. Delete any objects that do not relate directly to the issue.
6. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
7. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
8. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
9. Compile the code. (From the database window, click: Debug-->Compile)
10. Run the compact/Repair utility.
11. Remove any Passwords and/or security.
12. Post explicit steps to replicate the issue.
13. Test the database before posting.
In other words, ...post a database that we can easily open and immediately see/troubleshoot the issue, and if applicable, also include a Graphical representation of the Exact results you are expecting.
JeffCoachman