![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Hi, I have an application written in Access 97. The front-end and back-end are separated into two .mde files. I still have the original .mdb files. The problem is: I want to convert the application to Access XP. The front-end is no problem, but I'm worrying about the back-end: there has been added much data to the .mde back-end. How do I convert it to Access XP? It seems like Access XP can link to the A97 .mde and use it, but I would rather convert the .mde to AXP as well. Any tips on this? Thanks in advance, Pieter |
#2
| |||
| |||
|
|
I have an application written in Access 97. The front-end and back-end are separated into two .mde files. I still have the original .mdb files. |
|
NO Email Please. Keep all communications within the newsgroups so that all might benefit. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
On Mon, 03 Nov 2003 23:36:17 +0000, Douglas J. Steele wrote: And MDEs do absolutely nothing for data: there's no reason for the back-end to be an MDE. Doesn't it prevent users from altering tables? That's the reason I converted it to an MDE. |
#5
| |||
| |||
|
|
And MDEs do absolutely nothing for data: there's no reason for the back-end to be an MDE. Doesn't it prevent users from altering tables? That's the reason I |
#6
| |||
| |||
|
|
Hi, I have an application written in Access 97. The front-end and back-end are separated into two .mde files. I still have the original .mdb files. The problem is: I want to convert the application to Access XP. The front-end is no problem, but I'm worrying about the back-end: there has been added much data to the .mde back-end. How do I convert it to Access XP? It seems like Access XP can link to the A97 .mde and use it, but I would rather convert the .mde to AXP as well. Any tips on this? Thanks in advance, Pieter |
#7
| |||
| |||
|
|
There is absolutely no benefit to converting a back-end (data-only) file to an MDE file, so you might consider simply creating a new, blank MDB file and importing all of the tables, along with their relationships, from the existing back-end MDE and leaving it as an MDB. I must have misinterpreted the manual (or I haven't read it carefully :-) |
#8
| |||
| |||
|
|
There is absolutely no benefit to converting a back-end (data-only) file to an MDE file, so you might consider simply creating a new, blank MDB file and importing all of the tables, along with their relationships, from the existing back-end MDE and leaving it as an MDB. I must have misinterpreted the manual (or I haven't read it carefully :-) |
|
But your suggestion works fine, thanks! |
|
NO Email Please. Keep all communications within the newsgroups so that all might benefit. |
![]() |
| Thread Tools | |
| Display Modes | |
| |