Do any members of this forum use a CASE tool when they develope a database, or do you think it's a waste of time and money?
Is it over-kill to use a CASE tool on small non client-server projects?
Would using a CASE tool help bring my developer skills to a higher level?
I feel like a weekend hacker when designing my Access databases and think a more managed approach may be what I need, but it's a large investment in time and money.

Opinions Appreciated (before I invest).

Thanks.

No CASE tools are needed for an integrated (unsplit/desktop/non client-server) Access database. That's way overkill. If you need any of those features to document your project, use Visio. That is more than enough.

In fact, if you have Visio Pro, you can design your database in Visio, and then export it directly to Access and it will be built. You can also reverse engineer a database by pulling it into Access Pro, and it provides full documentation after the fact.

HTH


mmcdonal

Sorry, you can reverse engineer by pulling the database into VISIO Pro, not Access Pro.


mmcdonal

Wow, I'm glad I asked! I have Visio2003 and I'll check it out.

Thanks.

It must be Visio PROFESSIONAL. Standard will not work. But the upgrade isn't that much, and well worth it.

mmcdonal

I have used it as I download a master file from mainframe and due to some part identification process later on (in another process) they need to be Upper Cases only. This is very simple indeed:

Sub Capital()
Dim cnCurrent As ADODB.Connection
Dim rst As ADODB.Recordset
Set cnCurrent = CurrentProject.Connection
Set rst = New ADODB.Recordset

rst.Open "AllParts", cnCurrent, adLockOptimistic, adCmdTable

'Just choose column Type for the process
Do Until rst.EOF
    rst!Type = UCase(rst!Type)
rst.MoveNext
Loop

rst.Close
cnCurrent.Close
Set rst = Nothing
Set cnCurrent = Nothing

End Sub

Have fun
Axxess :) :)