🚀 go-pugleaf

Hi Ted,

"Ted Byers" <r.ted.byers@sympatico.ca> wrote:
>
>Hi Vladimir,
>
>What about my guess is this function:
>
>    void Disconnect(void) {
>      if (connected) {
>        connection.Exec(Function("Close"));
>        // is the following necesary - I doubt it (because
>        // of the bad effect of connecting to a DB with
>        // both the catalog and connection objects)
>        // but I want to be sure
>        catalog.Exec(Function("Close"));
>        connected = false;
>      }
>    };
>
>Is it right or wrong to call close on catalog if it has already been called
>on connection?

"Close" - is not property for Catalog object.

By definition method Create (Catalog) - creates and opens new 
connection (ActiveConnection property). But not every provider 
support creating new Catalog. So it is possible to call Create 
for Catalog then test Errors collection (Error object from ADO) 
and if all good use ActiveConnection else to use Open method from 
Connection object. 

    void Disconnect(void) {
      if (connected) {
        connection.Exec(Function("Close"));

// also possible :
        connection=Unassigned;
        catalog=Unassigned;
// now you can use VarIsEmpty(connection) or VarIsEmpty(catalog)
// for testing before using.

        connected = false;
      }
   };

By the way. Now I think about article for my site (automating 
for Microsoft Project). Can I ask you to read it and make your 
notes when it will be ready?

Best Regards,
Vladimir.