We recently upgraded from CF 9.02 to CF 2016 Update 15, and we noticed that the sender details of mails we send are in lowercase.
This is a snipet of the code: <cfmail from="info#sample.com (Info Sample) ... >"
The mail is received where the sender name is "info sample", so, converted to lower case.
Has anybody an idea why?
Thanks!
I found some kind of workaround. If I change the code from:
<cfmail from="info#sample.com (Info Sample) ... >"
To:
<cfmail from="Info Sample <info#sample.com> ... >"
The case is maintained. Has anybody an idea why they changed that? Or is it just a plain bug in CF2016?
Related
I have a macro that we were using for years and worked well in Excel 2010. However, now that we upgraded to Excel 2013, it gives a run time error 9.
The following code part is highlighted after debugging it:
Sheets(1).Copy after:=Workbooks(mfname).Sheets(3)
I know already that this error has to do something with the availability of the range. The question is if there is any easy fix to this? The relevant code-snippet:
Workbooks.Add
mfname= ActiveWorkbook.Name
Workbooks.Open template
template_name = ActiveWorkbook.Name
Sheets(1).Copy after:=Workbooks(mfname).Sheets(3)
Workbooks(mfname).Activate
Sheets(1).Delete
Sheets(1).Delete
Sheets(1).Delete
lapok = Sheets.Count
Thank you for the help!
I'm no expert in VBA, but little google searching says error 9 is subscript out of range error.
This likely is from Sheets(3). I also remember excel had 3 sheets open by default in those versions. Maybe that is not the case now, and causing the problem.
Hello,
My problem is that when i try to import an UDF in Ecxel 2013 I receive the error message can be seen on the picture. I have installed xlwings and it works except the UDF importing. Note that i used "xlwings quickstart myproject" so there is no problem with the file names and i also used the sample function so that should be fine as well
Thank you in advance for your help!
I currently don't understand why you get that error, but I should be able to tell you how you can work around it for now:
Open the file udfs.py in the xlwings package and remove the last argument on line 36, i.e. remove , ArgumentDescriptions=argdocs.
The intended functionality of that line (showing function argument description) is currently broken anyway (see here) so hopefully this will be resolved in a future version.
I'm using this code to loop columns of a SharePoint 2013 List.
currentContext.Load(currentList.Fields);
currentContext.ExecuteQuery();
foreach (Field f in currentList.Fields) {
}
No problem with normal columns. But, when I arrive to a lookup column I have this error:
"Unable to cast object of type
'System.Collections.Generic.Dictionary`2[System.String,System.Object]'
to type 'Microsoft.SharePoint.Client.Field'."
I found for example this discussion
This issue came when we were working with TaxonomyFieldValue fields. For us changing references was not an option. This helped:
TaxonomyItem dummy = new TaxonomyItem(web.Context, null);
It will force program to load adequate libraries forcing correct type in runtime.
I had this same issue and updating the references fixed it for me. This question helped me figure it out.
I went from version 14 of "Microsoft.SharePoint.Client" and "Microsoft.SharePoint.Client.Runtime" to version 16 and no longer had the error.
Latest client download
Problem with the S22.Imap:
xm003 BAD [CLIENTBUG] Command syntax error
my Search Condition from the Example:
IEnumerable<uint> uids = client.Search(SearchCondition.SentSince(new DateTime(2015, 10, 20)));
oll other SearchCondition's work fine. Pls Help.
The problem is that S22.Imap is sending an incorrectly formatted date string in the SENTSINCE search query.
Since S22.Imap is a dead project, I would recommend switching to my open source MailKit library instead.
Hope that helps.
I am connecting to ADS through ODBC DSN. Everything works well until I tried
out my Save Routine. Data is saved quite alright but I get an error that
says - "Option value changed". What could this be? Can't find in the help
file.
The full error message is:
ODBC - 2169
[iAnywhere Solutions][Advantage ODBC Driver] Option Value Changed.
I sent an email in respect of this to advantage#extendsys.com since this
error
number falls between error numbers: 2168 - 2188 Internal Error that should
be reported.
I posted this question on the Newsgroup without a possitive response.
Best regards,
Fredrick Ughimi
support#ughimisoft.com
For ODBC, in general, "Option Value Changed" typically indicates that a request was made that was not valid or not supported by the driver so the driver substituted similar value. Typically this type of error is informational or in other words sql_success_with_info. I suggest looking into an ODBC trace as it may help uncover what was changed or at least narrow down what was occurring.
It may also be helpful to post information about your save routine.