If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Import as substitute for Compact/Repair
I have a large db in production for a couple years. I recently converted it
to A2007, and the app keeps getting "out of memory" errors. I'd guess there is corruption. No other evidence of it so far. I do get errors from time to time due to an issue with Citrix and Remote Desktop (clipboard sync problems...), but I'm getting far more errors now than before...so, I thought I'd create a new A2007 db and import the entire backend (and ultimately the frontend to another new A2007 db.) I'm stumped though by the need to recreate all the relationships. Any shortcut or programmatic way to do that? -- Jim |
#2
|
|||
|
|||
Import as substitute for Compact/Repair
Afraid I don't have Access 2007 installed on this machine, but one of the
options in previous versions of Access was the ability to import relationships when you imported the tables. Are you sure that the back-end is the culprit of the "out of memory" errors, though? I would have expected the front-end to be generating them, since the back-end doesn't do anything! -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no private e-mails, please) "JimS" wrote in message ... I have a large db in production for a couple years. I recently converted it to A2007, and the app keeps getting "out of memory" errors. I'd guess there is corruption. No other evidence of it so far. I do get errors from time to time due to an issue with Citrix and Remote Desktop (clipboard sync problems...), but I'm getting far more errors now than before...so, I thought I'd create a new A2007 db and import the entire backend (and ultimately the frontend to another new A2007 db.) I'm stumped though by the need to recreate all the relationships. Any shortcut or programmatic way to do that? -- Jim |
#3
|
|||
|
|||
Import as substitute for Compact/Repair
I haven't done an import from 2007, yet and I don't have a copy I can test
with here at work, but I know that in 2003, when you get the import dialog up and select tables, there is an options button that allows you to select various things to include with the import, Relationships being one of those. Also, it may be necessary to open the relations window and click on Show All Relations to get them to show up in the new database. "JimS" wrote in message ... I have a large db in production for a couple years. I recently converted it to A2007, and the app keeps getting "out of memory" errors. I'd guess there is corruption. No other evidence of it so far. I do get errors from time to time due to an issue with Citrix and Remote Desktop (clipboard sync problems...), but I'm getting far more errors now than before...so, I thought I'd create a new A2007 db and import the entire backend (and ultimately the frontend to another new A2007 db.) I'm stumped though by the need to recreate all the relationships. Any shortcut or programmatic way to do that? -- Jim |
Thread Tools | |
Display Modes | |
|
|