[cvsnt] Re: Exporting access

[Martin Cole]

Exporting accessI am happy to share :)      - I copied the cvsnt list too, as it may be useful to others too :)

I have attached a class module to this email (email me back if it gets removed by antivirus). There is quite a lot of chaff in it, I was planning to export all form properties too I can strip it out for you if you want, but it is stable for what we do.

The invocation code is :

Private Sub cmbExportAll_Click()
    Dim clsExport As clsExportAll

    Set clsExport     Call clsExport.ExportCode
    Call clsExport.ExportQueries
    Call clsExport.ExportTables
    Set clsExport End Sub

I put a command button on my switchboard form (it can go anywhere).

It requires a folder called "Export" to be under the folder that contains the xxx.mdb file.

The export tables is hard coded to export the "Switchboard Items" table and a table that is specific to our database, so It would need to be modified, or commented out from the above code.

The ExportQueries, exports ALL queries that the project can see, including linked queries from mSQL (maybe oracle queries if they are visible) and queries that are embeded into forms... the Queries.sql file looks a bit strange at the start, but you will get used to it.

If you get really stuck, I can send you a test.mdb with the code in, and working.


Marts




  ----- Original Message ----- 
  From: Rodney Schuler 
  To: 'Martin Cole' 
  Sent: Friday, March 12, 2004 10:09 AM
  Subject: Exporting access


  > -----Original Message----- 
  > From: Martin Cole [mailto:martin at martinjcole.com] 
  > Sent: Friday, March 12, 2004 08:54 
  > To: cvsnt at cvsnt.org 
  > Subject: Re: [cvsnt] Help me understand cvsnt before it get dismissed 
  [SNIP] 
  > 4/ Kinda depends on what you need to know - With respect to 
  > our database 
  > code (in access) I implemented an export class that exports 
  > all queries, 
  > classes, and modules to text files in an ".\Export" folder 
  > and I keep these 
  > in cvs. This way I can use viewcvs to see code and sql 
  > changes. To get sql 
  > exported, it must be visible in the access frontend. 

  I am starting some access/sql-server projects that sound similar to yours.  I see the need for export-the-code functionality in access.  I have not done much access programming and have no idea how to begin to implement such a thing.  (All previous db work done with oracle)  Can you share the code, or give me a pointer to some documents/books to get started?

  Thank you. 

  -Rodney 
  ----- 
  Never be afraid to try something new. 
  Remember that a lone amateur built the Ark. 
  A large group of professionals built the Titanic.