I think you need to define your application name when you build your standalone app.
http://doc.4d.com/4Dv16/4D/16/CommonInternalName.300-3130143.en.html quote: > If this key is omitted and if none of the RuntimeVLInternalName, > ServerInternalName or ClientInternalName keys are passed, the internal name > associated with the 4D application is used. DISPLAY NOTIFICATION is probably just passing the internal name to its underlying native Windows API. if hadn't known of these build keys before, probably good time to change them from "4D". • CommonVersion • CommonCopyright • CommonCreator • CommonComment • CommonCompanyName • CommonFileDescription • CommonInternalName • CommonLegalTrademark > 2017/02/02 17:03、Piotr Chabot Stadhouders <[email protected]> のメール： > > Our customers don't know "4D Volume Desktop" > They start asking questions what this is > How can I get rid of this "4D Volume Desktop", and instead showing our own > application name 宮古 啓介 セールス・エンジニア 株式会社フォーディー・ジャパン 〒150-0043 東京都渋谷区道玄坂1-10-2 渋谷THビル6F Tel: 03-6427-8441 Fax: 03-6427-8449 [email protected] www.4D.com/JP ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
