A_GetADI_AskDup and A_GetADI_No_Dup not working

[ktrussell]

These macros give an error related to opening the file. I could see the problem being this line:

myFile = Worksheets("OM_Ct").Cells(1, 27).Value

I replaced that with these 2 lines copied from A_GetADI:
myDir = DownloadFolder()
myFile = myDir & Worksheets("OC_Config").Range("B5").Value

Then an error occurred in another place. I did not troubleshoot further.

Thank you for this great tool!

[x2rider]

Those functions are no longer needed or used and are no longer supported. To load your ADI file, use the buttons on the OC_Config page to: 1) Select ADI File 2) Read ADI File Paul Ka5pmv

…

On Tue, Jun 25, 2024 at 10:25 PM Kenny Trussell ***@***.***> wrote: These macros give an error related to opening the file. I could see the problem being this line: myFile = Worksheets("OM_Ct").Cells(1, 27).Value I replaced that with these 2 lines copied from A_GetADI: myDir = DownloadFolder() myFile = myDir & Worksheets("OC_Config").Range("B5").Value Then an error occurred in another place. I did not troubleshoot further. Thank you for this great tool! — Reply to this email directly, view it on GitHub <#16>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWHR7UYGXMV2JPD5ASBMCLZJIYDRAVCNFSM6AAAAABJ5AD63OVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TIMJQGMYTAOA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ktrussell]

OK. They sounded very useful to be able not to have to only export the new contacts, but instead to let the macro not import duplicates. I can work without them, of course.

Thanks!
Kenny
KT4X

[x2rider]

So you export all and load all in to add in the new ones? If that’s the case, and if that something people have done, I could add another button or checkbox that wipes the contacts before loading if that would do what you want, although you would have to make sure it’s a full file with all contacts. I was using the send to eqsl function in netlogger that marked records as sent by putting the letter E in one of the columns, then I knew if it didn’t have an E on the record, I haven’t exported them. It was a handy feature, but now my log4om sends all contacts to eQsl so I’m not sure if they check for dupes. Paul

…

On Wed, Jun 26, 2024 at 9:21 PM Kenny Trussell ***@***.***> wrote: OK. They sounded very useful to be able not to have to only export the new contacts and let the macro not import duplicates. I can work without them, of course. Thanks! Kenny KT4X — Reply to this email directly, view it on GitHub <#16 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAWHR7XWZ2LGIWQUI7CIAT3ZJNZI3AVCNFSM6AAAAABJ5AD63OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJSHEZDQNBZGY> . You are receiving this because you commented.Message ID: ***@***.***>

[ktrussell]

I am not familiar with the send to eqsl function. I will look at that. That should work fine. I try to export from Netlogger every day after I have added log entries. If I do that, I know exactly which contacts to select to do the export. If I miss a day or two, I have to search on your OM_Ct tab to see what is there, comparing the Netlogger. So, what I was planning to do wth the A_GetADI_NoDup macro was just grab some more than I know I need to export and let the macro keep out the dups.

But, I can keep doing what I am doing, or better yet, I'll use the eqsl function so I have that "E" flag to go by.

Thanks so much!
Kenny
KT4X