Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't have a great answer here.</p> <p>However, in the past I often made a "log book" of changes to tables and then simple used that on site.</p> <p>Do note that you can cut + paste macro code. And the code saves as XML.</p> <p>For example, this after update table trigger looks like this in Access:</p> <p><img src="https://i.stack.imgur.com/jf5VY.png" alt="enter image description here"></p> <p>If you cut out the above (ctrl-a, ctrl-cc),, then you can paste that into a note pad. In fact you can even paste/open it in visual studio or any xml editor, and you see this:</p> <p><img src="https://i.stack.imgur.com/cMhVe.png" alt="enter image description here"></p> <p>So you can cut + paste out of those macros.</p> <p>As noted, thus in the past I often kept a "log" of changes. </p> <p>So if I was working off site and I modified 2 code modules, 4 forms and 2 reports, then I had a little log of changes. I would type into this sheet what object was changed.</p> <p>When I get on site, then I quick glance at that sheet and I know to import the 3-5 objects and such a import is only a few minutes tops.</p> <p>However, with table triggers and store procedures, you could have more then just a few to copy.</p> <p>I would either do one of two things:</p> <p>Use the log idea and </p> <p>a) Un-publish the development version and bring that with me to your working site. You then import new forms, reports etc. For trigger code, you cut + paste between the two applications.</p> <p>b) When you make a change to a trigger, then cut + paste into a note pad doc and place them in a directory. When on site, simply take each notepad, cut + paste into production and then move or copy the notepad item into a "done" folder.</p> <p>The above is certainly less than ideal. Then again in the past I not always had code to script out a table change, and using a little log sheet worked quite well.</p> <p>So in the past I often just written down that such and such table was modified and I have to add such and such column.</p> <p>So it really your choice as to if you want to cut + paste out the macro code as xml into separate little documents, or cut + paste right out of development into production.</p> <p>I do think if you working in differnt location, then I think it likely best to un-publish the development version, and bring that with you (I assume you know/realaize that you can make a un-published copy of a web application).</p> <p>So the forms, code modules, macro's etc can just be imported rather easy (you delete the forms etc, and just import from that un-published copy).</p> <p>However, for the table code? You have to cut + paste from that un-published copy one at a time into some staging area, or as noted cut + paste between the applications.</p> <p>There is the possibility that save-as text might work here, but I not yet had the time to cook up a better solution.</p> <p>Edit: By the way, in above I assumed a web services database, but the advice still applies to non web Access databases.</p>
    singulars
    1. This table or related slice is empty.
    1. POhow to export Access 2010 data macros
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAlbert D. Kallal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhow to export Access 2010 data macros
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your time and for all the detail Albert. The XML info is really useful. Also Ctrl-C, Ctrl-V works really well too. Based on your reputation, I'm taking this as the gospel answer. Thanks again
      singulars
      1. PO
      1. USunrazzle
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload