MS Access - call this a database?
Mar. 7th, 2010 10:38 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I'm not sure I believe this. Using MS Access as a backend DB for a "teach myself" CF site, and my next trick is to move all my existing queries into stored procedures. It's been a while since I used Access, and I couldn't remember how it handled them. After a bit of Googling, I now know why: it doesn't.
Oh, an Access stored proc can exist: I just created one. But you can't do it through the huge, bloated, over-complicated user interface. Not even in SQL edit mode: it looks at "create proc" and decides it's a "create table" with a syntax error. No, you have to attack it through some other interface (ColdFusion and a cfquery tag, in my case) to get the SQL to create the stored proc to run.
They expect this to be taken seriously???
I can feel a CF app for writing and testing Access stored procedures coming on....
or maybe I get tempted into MySQL?
Oh, an Access stored proc can exist: I just created one. But you can't do it through the huge, bloated, over-complicated user interface. Not even in SQL edit mode: it looks at "create proc" and decides it's a "create table" with a syntax error. No, you have to attack it through some other interface (ColdFusion and a cfquery tag, in my case) to get the SQL to create the stored proc to run.
They expect this to be taken seriously???
I can feel a CF app for writing and testing Access stored procedures coming on....
or maybe I get tempted into MySQL?
no subject
Date: 2010-03-07 02:06 pm (UTC)They all have their pros & cons, but MySQL is probably the easiest to get into.
no subject
Date: 2010-03-07 07:11 pm (UTC)no subject
Date: 2010-03-07 08:30 pm (UTC)This is a simple DB, the conversion wouldn't take long. Data transfer, there's only one table too big to be done manually.