Re: Gendbc - produces incomplete program

Olaf,

> Okay, I didn't make it obvious enough:

Sorry if I'm appearing a bit simple.

> Replace every EXCLUSIVE with SHARED in the
> gendbc.prg and comment the line (I assume line
> 290):
>
> COMPILE DATABASE (m.g_cFullDatabase)
> =>
> * COMPILE DATABASE (m.g_cFullDatabase)

OK, done these. although I had already tried
opening the DB exclusive.

> THEN you can run gendbc on open DBCs too.
>
> And a DBC open shared cannot change it's
> structure,
> so it is also no danger, that the database
> could change
> during it's analysis by gendbc...

Very good point.

However we may be getting slightly off the point.
I had actually managed to get it to run *before*
contacting the group, but it produced incomplete
code, without errors being reported.

As I said in my original post, even following your
worthwhile modification to the program and
creating an empty folder with only gendbc.prg and
..krt files in it produces only an empty database,
without even the stored procedures from the krt
file.

Cindy Winegarden tried it on the northwind
database to produce 1600+ lines of code, on my
machine it produced 90+ lines. The
MakeTable_Table/ViewEtc procedures are missing.

It looks like I will have to either google for a
later version or SET STEP ON and crawl through it
and find the fault. It's usually my fault in the
end. :-) Even after 20 years with fox! I was
hoping for a brain pain free solution.

Thanks very much for your time.

regards
Alan
.

Relevant Pages

  • Re: Database Model - Class, objects and interaction
    ... I was just proving stored procedures can call views. ... stuff like security and logging. ... So given 100,000 users, you would create database accounts for each? ... Part of our system's integrity was its reliability, and reliability is often assisted by simplicity. ...
    (comp.object)
  • Re: Database Model - Class, objects and interaction
    ... Stored procedures should only be used as a last resort if you cant use ... I've not said that views shouldn't be created, only that they shouldn't be exposed as the interface to the database. ... But business rules can be more complicated than simply defining overdue invoices. ...
    (comp.object)
  • Re: Infinite Loops and Explicit Exits
    ... the whole payroll system would be dependent on proper database ... I design large systems the same way. ... Stored procedures ARE application code. ... any language, including Cobol. ...
    (comp.lang.cobol)
  • Re: Identity Column
    ... the end use is using Crystal Reports - where is the magic? ... The user will connect using Active Directory from their desktop to the database server or do please explain the magic.... ... Using stored procedures you permission on the stored proc only; the user can only execute the stored procedure with the parameters defined, there is no select * from to get all the information in your database. ...
    (microsoft.public.sqlserver.programming)
  • Re: Infinite Loops and Explicit Exits
    ... The behaviour could only be changed by changing the database. ... >>designing proper databases and using stored procedures on them, ... are database dependent and not available in COBOL. ... But with extended SQL you simply write the procedures in SQL ...
    (comp.lang.cobol)
Loading