microsoft access front end

[actiondave]

Currently I am using a predictive dialer that is just the "dialer" with reporting capabilities. (using a completely seperate database)

Once a live call is determined, it is sent to an available agent which then populates a "key" number on my microsoft front end form and then opens a form approriate to the campaign that connected with the information for that customer.

The dialer runs .ini file that looks for my application to populate the key and my form opens.

My question is...Is this possible to do using vicidial. This would make my initial transition to vicidial seamless until progressing further with php.

If it can be done and a cost associated, please pm me.

thanks




_____________________________________
Test Machine Setup:

Intel Pentium 4 CPU 2.80GHz

GoAutoDial CE 2.1
Vicidial SVN 2.4-309a BUILD: 110430-1642
Asterisk 1.4.39.1-vici
Dahdi 2.4.1
CentOS 5.6

[williamconley]

Thank you for posting your installation method (GoAutoDial CE2.1) and your Vicidial version with build. And even your asterisk and Dahdi versions. Cool.

Yes, the situation you describe is part of Vicidial. Download the manager's manual from eflo.net and you will find a great deal of useful information. Purchasing the paid version is not a bad idea either.

The "Web Form" setup will open any web page you like at the beginning of any call (or during, or after, depending on how you want to use it) automatically or at the press of a button on the agent's screen.

The Script tab can be populated with information from the Lead record and is also fairly easy to use.

Consider also that there are three basic methods of installation:

GoAutoDial.com's .iso, Vicibox.com's .iso and "From Scratch" which has several directions on several sites (including the Vicidial Wiki).

GoAutoDial has a pretty agent screen, but that screen is not compatible with the Developer Trunk (version 2.4, which most installers are using at present) but is compatible up to version 2.2.1 (which is what it installs). Vicibox uses all stock installation screens and CAN install 2.2.1 or 2.4 with SVN control (version control, easing upgrade) and will also install a Clusterable solution (multiple servers acting as a single unit to increase capacity).

And to be clear: GoAutoDial installs on CentOS which is not supported by The Vicidial Group (and therefore limits your "help" to Gardo, myself, and a short list of others), whereas Vicibox is supported by The Vicidial Group and virtually every other Vicidial Professional out here.

Welcome Aboard. Happy Hunting.

[actiondave]

I purchased the manager manual but....

This isn't to open a web page. I want it to look for an application (microsoft access) that has a form (customer) with a field (key) waiting for input from the dialer.

Once the dialer connects a "live" call, sends it to the agent and then sends the "key" via keystroke (at the moment) to the application (microsoft access) which then opens the correct form with customer info showing.

Are you saying this can be done with vicidial or only "web pages"

thanks

Also, GoAutodial is just for initial testing. I will be try the other solutions also before using in production.

Quite impressed so far as I test, read, read and read...........


_____________________________________
Test Machine Setup:

Intel Pentium 4 CPU 2.80GHz

GoAutoDial CE 2.1
Vicidial SVN 2.4-309a BUILD: 110430-1642
Asterisk 1.4.39.1-vici
Dahdi 2.4.1
CentOS 5.6

[williamconley]

Convert your Access application to SQL and put it in a web and you'll be rockin.

Otherwise, you'll need to create an app that will perform this task manually, and it would be interesting to do, but the amount of work involved to allow this access app to run would be prohibitive if you consider the limitations inherent in Access (which will limit the useful lifetime of the app to begin with). You could have the page "force download" a specific file which is of a particular "mime type". Then associate an app with that mime type and have that app fire up access and pass the data (which would presumably be in the doc that was fired up by your cool new app).

But converting your Access to SQL would allow the data to be web served and shared by an unlimited number of users without crashing the database or scrambling the data or having sync issues.

I have spent a LOT of time with Access programming, and am now in Full Recovery. First I converted everything to SQL, which I love BTW, but then found MySQL to be much more cost-effective ... and now it's all we use. We actually retired our last Microsoft Server last year. (Noone was using it!)

[actiondave]

thanks for the help William...appreciate it

BTW...my db is in sql but i use forms in access as a front end.

The dialer I am using right now has to have certain parameters downloaded each day as to what numbers to dial per campaign and then when dialing that campaign it populates the key number into a microsoft access form that has only one field on it. The "key" field.

The script populates the key number then enter....and walla the correct form opens with the customer information.

The dialer has its own application that runs while the microsoft app is open.

[williamconley]

If you build the app, lemme know how it works out. Interested to hear.