Hi Christian- thank you for submitting this ticket. In order to best troubleshoot, I'd like to have a copy of the VCF file you are using. Would it be possible to email that to me at ghadlock<at>gmail.com?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Christian, another update for you. The problem is that the program is expecting to find the string CHARSET=XXXXXXX;" in the Encoding Printable section of the vcards where XXXXXX represents the character set used for encoding, but there is no semicolon after the character set used in your file so the program didn't handle that scenario previously. I'd still like to get your VCF file to ensure I properly handle the character set and don't leave any "garbage" in your output, but for now I've created a test version of the program for you to try. This version will bring up a message box every time it encounters that scenario and if you could email me the screenshots of the message box then I should be able to close out the changes. Again, the VCF file is preferred but this is a second option that will allow you to import your file and also give me some more information to refine the code. You can download this version here: https://www.dropbox.com/s/vlc51963npy2kdo/VCF%20Import%20v3.4%20DEVEL.xlsm?dl=0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I really appreciate you providing the vcf file as it contained several VCF fields not specified in the VCF 3.0 standard and those resulted in "noise" in the output. All fields are now appropriately handled and the output looks good. Thank you again for taking the time to report the issue and supporting additional development and testing. I'll update the files section later today with the new version provided above.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Christian- thank you for submitting this ticket. In order to best troubleshoot, I'd like to have a copy of the VCF file you are using. Would it be possible to email that to me at ghadlock<at>gmail.com?
Hi Christian, another update for you. The problem is that the program is expecting to find the string CHARSET=XXXXXXX;" in the Encoding Printable section of the vcards where XXXXXX represents the character set used for encoding, but there is no semicolon after the character set used in your file so the program didn't handle that scenario previously. I'd still like to get your VCF file to ensure I properly handle the character set and don't leave any "garbage" in your output, but for now I've created a test version of the program for you to try. This version will bring up a message box every time it encounters that scenario and if you could email me the screenshots of the message box then I should be able to close out the changes. Again, the VCF file is preferred but this is a second option that will allow you to import your file and also give me some more information to refine the code. You can download this version here: https://www.dropbox.com/s/vlc51963npy2kdo/VCF%20Import%20v3.4%20DEVEL.xlsm?dl=0
Thank you. Find it here https://www.dropbox.com/s/xt7h27t381l7j3z/debug.vcf?dl=0
New version throws some charset errors. I assume on pictures. Rest is fine.
Thanks Christian- I'll have an updated version for you tomorrow to accommodate this file format.
Hi Christian-
The new version is complete and available here: https://www.dropbox.com/s/d3h4g1mfqvfas1u/VCF%20Import%20v3.4%20FINAL.xlsm?dl=0
I really appreciate you providing the vcf file as it contained several VCF fields not specified in the VCF 3.0 standard and those resulted in "noise" in the output. All fields are now appropriately handled and the output looks good. Thank you again for taking the time to report the issue and supporting additional development and testing. I'll update the files section later today with the new version provided above.