Transfer All Data

Author:  Eric Vasbinder

Support Status:  APPROVED

Integration Method:  ODBC Direct Database

Connection Methods:

• PREFERRED:  TLS Database Endpoint (TLS VPN)

• IPSEC VPN

Hosted:  NO

Hosting Location:  Client Side Microsoft Excel Plug-in Connector, hosted on customer workstations, connected over TLS Database Endpoint (TLS VPN) or IPSEC VPN.

Additional Charge:  NO (VPN add-on included in every cloud contract by default - if not on your contract, additional charge will be required to add VPNs)

Vendor URL:     https://transferalldata.com/ 

Product Use Case:

Exporting/importing data between Vista and Excel.   This tool replaces the "Export Grid" option on Vista forms, and avoids the need to modify Crystal Reports to export cleanly to Excel and provides missing Import templates in the Import module.  Features also exist for full Financial Statement downloads and data conversions.

Similar Products:

This product is similar to and competes with other Excel add-on SQL query builders, such as Insight Software Spreadsheet server.

ERP Connection Overview: 

As per many other server-side integrations to third-party products, this product is designed to talk to Vista's database directly using ODBC.  This connection requires that the Vista server be "visible" to the third-party system.  To ensure that the two systems can communicate, we set up either a TLS Database Endpoint (TLS VPN) or a server-to-site IPSEC VPN between our cloud and the vendor's on-premise environment where local workstations can connect to the Vista server.

NOTE:  This integration REQUIRES that any user of this tool have either TLS Database Endpoint (TLS VPN) or IPSEC VPN connectivity to the Vista server.  Thus, those end users are prevented from using Vista from anywhere in the world as per normal VRL-based cloud advantages.  Instead, the end users will most likely need to be connected to their company's corporate client VPN to allow for their workstation to see Vista.

Deployment Methodology:

We do not support hosting of this product in our cloud.  As such, the customer must continue to host the actual program (i.e. "bits") in either their on-premise environment on their local workstations.  As a result, since this product and Vista will be on separate networks, a VPN is needed to bridge the gap between the two networks.  

Detailed Instructions:

• 1. Stand up remote connectivity to our cloud:

     1. (PREFERRED) TLS Database Endpoint (TLS VPN) with the remote, public, static IP of the vendor's cloud added to the pre-approved list for the customer's environment:  TLS Database Endpoint 

        1.  OR

     2. IPSEC VPN between hosting location of third party product and customer's Vista environment in our cloud:  How do I set up an IPSEC VPN to access my Vista database directly?

  2. Create SQL account to allow third-party to authenticate to Vista:  I need a dedicated SQL account for my integration to Vista in your cloud. How do I set that up?

  3. Configure the third-party solution to talk to the IP address of the new Vista server in our cloud.