Quote:
Originally Posted by toddnorr
I am not completely sure I understand what your question is. What I think you are saying is that once you do the SQL dump you are having to create an extensive macro to get the data into Access and run that macro each time you dump.
If that is indeed what you are doing then it is similar to what I was doing. I found thought that it was easier to export to a CSV file and link the tables I wanted in Access to the files in the import_export folder. Doing it this way I do not have to run code each time I dump to update the Access tables.
Hope that made some sense. If not let me know and I will try again.
Good Luck!
|
I suppose linking it would make things a bit easier, but right now, I am trying to get all the years into a single database, which has become a bit of a complicated project. Basically, I have to add year fields to any place where there are no years and such. In this case, I need to have the data in unalterable tables rather than linked. I actually haven't worked on this in several weeks, so I've gotten a little fuzzy on exactly what I was doing now.