I would like to ask (if possible) to include network places in the "browse for folder" dialog of the txt/csv file location.

Please create a support ticket for that. tia.

I have noted that network shares are unavailable when WLP Is run as administrator. Is that intentional?

At first your post has confused me into thinking that if you run WLP as regular user network shares are available. I don't think that support for network drives has been ever added to the ASCII provider. As a workaround, you could create a "Network" folder/disk shortcut on your disk, save it, and choose it when required:

http://www.sevenforums.com/tutorials/49210-network-folder-shortcut-create.html
http://support.microsoft.com/kb/308416

Eugene, That may be another way to do it. I've always mapped a shared network drives in Windows Explorer for datasource access.

http://pureinfotech.com/map-network-drive-windows-10/

Today after installing 6.9.18 I noticed that WLP would not recognize the mapped network drives when started with "Run as Administrator". When started normally, WLP does enable creation of a mapped drive datasources. So it is working again.

I went thru a similar exercise with previous editions but today the "Run as Administrator" limitation seemed odd and not mentioned anywhere. I documented here for reference and possible fix.

So bad we don't have a split thread feature to "spin off" your question and rename appropriately. It might be difficult for others to find your reference to a mapped network strategy (?) issue here in an ASCII data provider related thread.

QUOTE:
Today after installing 6.9.18 I noticed that WLP would not recognize the mapped network drives when started with "Run as Administrator". When started normally, WLP does enable creation of a mapped drive datasources.

There's nothing to fix as it's not broken:

How to make elevated programs recognize network drives

Thanks for the reference to Windows elevated program work around. It answers my question on why the mapped drives were unavailable in the ASCII Provider and it is a Windows not a WLP ASCII Provider issue.

Perhaps the original poster or another will see that the ASCII Provider does support ASCII datasources via mapped network drives. This satisfies the OP request to include network shares. No development needed.