In message <[log in to unmask]>, Roy Brown
<[log in to unmask]> writing at 01:30:31 in
his/her local time opines:-
>In message <[log in to unmask]>, Alan Yeo
><[log in to unmask]> writing at 20:25:19 in his/her local time
>opines:-
>>Connie
>>
>>I have never tried using Visio to document an image database before,
>>but thought I'd take a quick look to see how easy difficult it was.
>>
>>Questions
>>
>>1) I assume that on your HP3000 you have an IMAGE/SQL DBE generated
>>that contains all the databases you want to document? If you haven't
>>stop now and do as Denys suggests except I think there may be a better
>>way by cutting and pasting from an FO Sets into Visio.
>
>One database, fine; but 17?
>
>>2) If you have a DBE set up, I assume that you already have some
>>simple Microsoft Query's set up on your PC that access the databases
>>via ODBC. If you haven't, then probably stop now and do it manually.
>
>>3) If you have got a MS Query set up try it in Excel first just to see
>>that you have connectivity, if you haven’t well....
>
>>4) I found in vision that going to the database drivers via "options"
>>under "database" it didn't seem to want to let me define/add an ODBC
>>driver that I have that explicitly works with Image/Allbase. So as a
>>guess when doing the reverse engineer I selected "Generic ODBC" it
>>worked. You then need to select a MS QUERY that you have already
>>defined that accesses that data source. (see 2 above if you haven’t
>>then probably too much work at this stage, but maybe not if you know
>>what your doing)
>
>>5) Magic it reversed engineered all the tables from a database that I
>>had a query datasource defined for.
>
>>Now the bad news what you get are a whole load of visio boxes drawn
>>for you with a list of all the items in each table/dataset. It
>>certainly hadn't managed to reverse engineer the index paths.
>
>>So as far as I can see the magic reverse engineer function in visio is
>>going to give them what you have already given them, but with a box
>>drawn around each table, upon which you are going to have to add the
>>index paths anyway.
>
>>Sorry but I'd say even if you get it working it ain't going to be the
>>answer.
>
>>Alan
>
>Hi Alan
>
>Good work!
>
>But according to the Help for Reverse Engineering, what you get depends
>on the capabilities of the ODBC driver and the DBMS. We know Image
>should be able to provide the keys, so maybe that Generic ODBC driver
>didn't have the welly that the MB Foster driver has?
>
>Anyway, I have another cunning plan, if you could bear to check this
>out for me, much of which is covered by the groundwork you've laid
>above.
>
>Basically, it's to do the same, but with MS Access, and import your
>test database into that, with the same ODBC driver, or better, your
>Image/Allbase one, if it will allow that.
>
>If it does the import, then Database Tools/Relationships should give
>exactly the diagram that Connie needs.
>
>The only(!) downside to this method is that it will import all the data
>from the database, not just the schema, so it probably needs to be done
>with small or empty databases. But if it works, I'm sure Connie could
>use test databases, or even generate some new empty bases from her
>schemata to use.
>
>I though I'd ask you to try this before suggesting it to her, in case
>it doesn't work.
>
>But if it does, we can let Connie know; and I'd hope that the CFA would
>be able to make Access available to her, if she hasn't already got it,
>in the same way they did with Visio Professional.
>
>Best Regards
>
>
>Roy
Oops, this was meant to be an email to Alan, not the list, but the cat
is now out of the bag :-)
Can you all (except Alan, of course) pretend you haven't seen it unless
and until we can report if it works or not?
Roy
--
Roy Brown 'Have nothing in your houses that you do not know to be
Kelmscott Ltd useful, or believe to be beautiful' William Morris
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|