Hi Garrett.
There are two ways of doing data capture using Query Builder:
1: Create the queries and install them on a client on the customers' network. The application can be run utilizing the built in scheduler, which in essence logs in as a specified user, runs the query and dumps a flat file to a predefined folder on the client. In the past, we created a custom sql connector to encrypt and upload the data from that folder on a matching schedule to a server on our network. The pros to this method are:
i> No VPN required as all the networks I have encountered dont engage in outbound filtering of traffic
ii> Can be scheduled to run at all hours, with any frequency with little to no intervention from the dealership staff (aside from the odd reboot)
Cons:
i> You are relying on a machine existing unmolested and powered up on a clients network
ii> Hardware failures require a site visit
iii> Without a remote access client of some sort the scripts are not adjustable without a visit (ie if you need to change the data you are pulling)
2: THe second method would require you to use a VPN to connect to a client network to run a query on a locally installed eralink, obvious advantage is you can change scripts and frequency rather easily, data is gathered local on your machine. Cons are dealers sometimes dont have routers configured or able to run VPN client tunnels, may require 3rd party assistance.