I have a very mundane question.
I have an database application concerning a breed of dog that runs on a server in SQL. I've always been able to use Alpha 5 for the database administration kinds of issues. We have almost 1500 users but only I get into the files to "fix" things when they are broken. For instance, last night I ran a query looking for dog's records in which the whelping date had been entered as D/M/Y rather than the specified M/D/Y format. I didn't get all of them but the egregious errors were caught. This query only required about 2 minutes to build and wasn't worth effort from my SQL programmer (a volunteer).
Now I need to greatly expend the concept and have found that I need a second volunteer. I found him but, he's only comfortable in MySQL.
The interface between the two "modules" should be simple. On the SQL side there'll be a menu choice that takes the user to the MYSQL module. To return, a MySQL menu choice will take the user back to the SQL module. There will be very little, if any, data exchanged between the two modules.
Our current host will be happy to host both.
The only two questions I have are: 1) Will I be able to use Alpha 5 (Ver 11) to access both the SQL and MySQL modules as needed. 2) Is there any issue I need to know about before I initiate the project for the MySQL module.
The SQL volunteer is getting busy in her own job and isn't able to support this relatively large expansion of the project. Thus, I have to do it the SQL/MySQL way or not do it.
I probably didn't ask this well but I hope you can get the gist of the issue.
Thanks.
Eric Johnson
I have an database application concerning a breed of dog that runs on a server in SQL. I've always been able to use Alpha 5 for the database administration kinds of issues. We have almost 1500 users but only I get into the files to "fix" things when they are broken. For instance, last night I ran a query looking for dog's records in which the whelping date had been entered as D/M/Y rather than the specified M/D/Y format. I didn't get all of them but the egregious errors were caught. This query only required about 2 minutes to build and wasn't worth effort from my SQL programmer (a volunteer).
Now I need to greatly expend the concept and have found that I need a second volunteer. I found him but, he's only comfortable in MySQL.
The interface between the two "modules" should be simple. On the SQL side there'll be a menu choice that takes the user to the MYSQL module. To return, a MySQL menu choice will take the user back to the SQL module. There will be very little, if any, data exchanged between the two modules.
Our current host will be happy to host both.
The only two questions I have are: 1) Will I be able to use Alpha 5 (Ver 11) to access both the SQL and MySQL modules as needed. 2) Is there any issue I need to know about before I initiate the project for the MySQL module.
The SQL volunteer is getting busy in her own job and isn't able to support this relatively large expansion of the project. Thus, I have to do it the SQL/MySQL way or not do it.
I probably didn't ask this well but I hope you can get the gist of the issue.
Thanks.
Eric Johnson
Comment