goprasad
asked on
Difference between MS Access mdb and MS Access ade files
Hello there,
We will be using a 3rd party MS Access developed application to be delivered via Citrix XenApp 4.5 published app. He has given us mdb application files, and when asked to generate ade files so that we can use in command line parameter in Citrix published app, he expressed his inability saying that, his application is not designed to generate ade files?
I would like to know the basic difference between mdb and ade files, and what is the pre-condition to generate ade files?
Thanks
ks
We will be using a 3rd party MS Access developed application to be delivered via Citrix XenApp 4.5 published app. He has given us mdb application files, and when asked to generate ade files so that we can use in command line parameter in Citrix published app, he expressed his inability saying that, his application is not designed to generate ade files?
I would like to know the basic difference between mdb and ade files, and what is the pre-condition to generate ade files?
Thanks
ks
Most .mdb files can be converted directly to an .ade file (AFTER moving the data to the SQL Server platform, as suggested by thekeyboardwizard above), but my question is why would this be necessary to do so? Citrix can run .mdb/.mde files (I am working with a client on the Citrix system now, and we're working with .mde files), and unless you're planning on upsizing to SQL Server, then you really don't have any need to run the .adp/.ade format.
LSM--I'm curious about this myself, but also want this answer for goprasad -- aren't mdb files unprotected? Can't the user just hit the F11 button and have access to the design?
Thanks,
jr
Thanks,
jr
If by "unprotected" you mean could a user make changes then: Yes a file in the .mdb format would be unprotected. You would be able to open this file and make any changes you wish assuming (a) you are working in a Full Retail version of Access and (b) the .mdb file is not secured with User Level Security or a Database Password.
OK Thanks--I wasn't certain. So goprasad, that's a compelling reason to go with ade files, unless there's only one or two "safe" users accessing the mdb. I don't know of any "prereq" that would inhibit ade's unless perhaps your third-party consultant didn't use SQL.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Though explained, the underlying difference was not made clear
Then you link in SQL server and you get an ADP file which is like the MDB but linked to SQL. Finally if you compile the SQL one you get an ADE file which is the source protected SQL linked database.
The issue is if you write an MDB file changing it 1st to ADP might well kill some scripts as they run differently, you can use the upsizing wizard to try this. If you make it to an ADP file then the ADE is no problems it will work ok.
I'm guessing your guy is struggling to get from MDB to ADP as his programming is crashing and may need a re-write.
~~thekeyboardwizard~~