![]() ![]() If you like presenting the keywords on reports as a comma-separated list (as you're currently storing them), you can write a simple function to do the concatenation for you at the presentation layer of your reports (concatenation functions for that purpose are a frequent Access question here on Stackoverflow). You could then use a subform with a dropdown list to populate each row of the join table. This "joins" the two, and would then give you a list. You really should use a proper many-to-many structure, with an additional table between the one where you're currently storing the keyword memo and your keyword list table. What if you have 100s of thousands of records and you want to search this field with LIKE "*Keyword*" - will it bog down to be terribly slow (no indexes, and not used well even if there were)? What if you want the keywords to be sorted in alphabeticsal order? This is a denormalized way to store the data, and this leads to problems: Now, all that said, I'd completely recommend against doing this. and you'd want to add the requery to the OnCurrent event of your form, as well (so that when you arrive on a record, the combo box already omits any keywords that are already in the list). This is effective upon Edit > Replace with Source, Edit > Insert Source, and when entering a segment when Options > Editing Behavior > Insert. at the end of the AfterUpdate code above (inside the End If): Private Sub cmbChooseKeyword_AfterUpdate() WHERE InStr(Forms!MyForm!txtKeywordMemo, tblKeywords.Keyword) = 0 You'd also want the rowsource of your combo box to not list items that are already entered, so this is one way that would work for a relatively short list of keywords: SELECT tblKeywords.* Me!txtKeywordMemo = (Me!txtKeywordMemo + ", ") & Me!cmbChooseKeyword Something like this: Private Sub cmbChooseKeyword_AfterUpdate() It could be very useful when there is no (sentence) match in the translation memory.It would be complicated to do it with a single control, but with two controls, a dropdown list for choosing the value to add, and a textbox displaying the memo field, you could have the combo box's AfterUpdate event append a comma and the chosen value to the existing data. ![]() For me 4th version, a word-based translation would be optimal, I mean (when I arrive to the given section) I want the software to automatically insert the source text to place of the target text, and translate those words which are known by the glossary. ![]() double-clutch automatic transmission, spring-preload etc.) so it would be useful to have this.Īs I know, now the user have three options, what he wants to see in the place of target text when he arrives to a new sentence: empty space, source text or fuzzy. Target: Three bonitas blonde chicas caminando on the shore y think on me. Source: Three beautiful blonde girls walking on the shore and think on me. I want OmegaT to automatically translate those words which have 100 percent (could be changable) match in the glossary. (if I'm not understandable, please read our conversation at the Yahho OmegaT group: ) ctrl+space and autocomplete on enter is okay, but robs time, for me an automated method would be much more faster. glossary based autotranslation when there is no (sentence) match in the translation memory double line spacing (easier for the eyes) ![]() There are only two things missing for me: Request from user (double-spacing crossed out as it needs to be in a separate RFE):įirst of all please let me congratulate for the software, it's really useful and logic, makes my work much easier. ![]()
0 Comments
Leave a Reply. |