MartyConnelly
martyconnelly at shaw.ca
Sun Dec 31 18:49:37 CST 2006
I think Microsoft did it this way in oder to save all DAP's, relationships, references, tables and command menus. It would require a boatload of code to do this in text files. So it just saves them to a basic mdb file with everything else stripped out like forms and queries. It achieves the same result as text file but simpler. You could export the tables as say a csv text file but that has it's own problems dropping formatting to only two decimal places and handling of binary OLE fields. Martin Reid wrote: >Marty > >Can you explain a little. I have based the intro on the templates on the save as text stuff. This is the copy edit stage so cant change to much. > >Oh ny the way Gustav even with the typo fixed the procedure still fails! > >Martin > >Martin WP Reid >Training and Assessment Unit >Riddle Hall >Belfast >Saving tables is the one exception to this method instead use the >DAP pages method, it is a carryover from the original Access 97 method >where it was really undocumented as opposed to just MS undocumented. >I got the original hint from Larry Lawson. > > 'This saves all tables, references, relationships, > ' DAP's and command menus to one file. > > SaveAsText acDataAccessPage, "", strPath & "dbAllTablesText.txt" > > 'Save only once to one file so exit. > ' the constant acDataAccessPage doesn't exist in Access 97 > ' so use the magic number 6 > >Also you may not want to save temp Queries so > > If dbs.QueryDefs(i).Name, 1) <> "~" Then > 'remove temp queries from selection > > >'using acTable = 0 with SaveAsText 'Tables won't work in 2003 or 97 > ' you will get saveastext 2487 error. > > >Martin Reid wrote: > > > >>Just fixing some stuff up. ANyone any idea whats the problem with this. It fails as soon as it tried to export the tables. >> >>Martin >> >> >> -- Marty Connelly Victoria, B.C. Canada