Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old April 14th, 2004, 05:49 PM
Authorized User
 
Join Date: Apr 2004
Location: , , .
Posts: 26
Thanks: 0
Thanked 0 Times in 0 Posts
Default ADE file in Access 2000 <---> Access XP

While reading Access help I found the following, and was
wondering if I got it right:

Quote:
"
Caution You won't be able to open, convert, or run code
in a Microsoft Access 2000 ADE file in future versions of
Microsoft Access. The only way to convert a Microsoft
Access 2000 ADE file to a future version will be to open
the original Access project the ADE file was created from,
convert it, and then save the converted Access project as
an ADE file.
"

So if I've developed an ADE file in Access 2000, would my
clients who run Access XP be able to use it ?

It sounds like the wouldn't. But they would be able to use the ADP file, correct ?

Reply With Quote
  #2 (permalink)  
Old April 14th, 2004, 08:17 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Location: Clarksville, TN, USA.
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Yes, your users will be able to use the ADE file. An ADE file is a compiled ADP just as a MDE file is a compiled MDB. Compiling the file removes the code from the original file,so if you need to make changes to your file you will need the original file that you used to create the ADE file.

Make sure to keep copies of your adp/mdb files before you compile them to make wure that you can make changes.

Security with ADP/ADE files is more important because users will have access to the SQL Server tables, view and stored procedures. You have to make sure that when you distribute this files, your users can not access the database window.

Your users can use either an adp or ade file and reach the database as long as they have rights within SQL Server.



Sal
Reply With Quote
  #3 (permalink)  
Old April 14th, 2004, 08:38 PM
Authorized User
 
Join Date: Apr 2004
Location: , , .
Posts: 26
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi Sal,

Good to know that I don't have to compile and distribute 2 version of the ADE file (one 2000 and one 2002/XP). That paragraph in MS help was poorly worded or I missed something.

The rights within within SQL Server for the users will be db_reader and db_writer so they cannot make schema changes.

The DB window will be hidden, and my custom menu won't allow them to unhide the regular toolbar.

I guess I should disallow the bypass key too, even though it's an ADE.

Reply With Quote
  #4 (permalink)  
Old April 14th, 2004, 09:06 PM
sal sal is offline
Friend of Wrox
 
Join Date: Oct 2003
Location: Clarksville, TN, USA.
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hold that tought. I read wrong, but, I have distributed 2000 MDE files to users who only have XP and the files run properly. As far as ADP files, I have not had to re-distribute 2000 files to xp users. I do remember that Access 2000 ADP files have more functionalyty as far as the canned ability to manage SQL Server permissions, so it will leave room for trouble, also the views and stored procedures are shown differently. XP does have more capability for stored procedures.

I am not sure if the file would crash for sure. Try this site and you may find out more.

www.accessvba.com

They have a section for client server apps (adp). Since your users will not be changing design items, they may be ok, but that is only a guess.





Sal
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
<bean:message key="error.access.rights"/> sparun1607 Struts 1 September 23rd, 2011 03:08 AM
HELP - Access 2000 Runtime w Windows XP Compiled.. chasidim Access 2 April 3rd, 2006 11:06 AM
<style> tags in a <body> vs. <div> bcat BOOK: Beginning CSS: Cascading Style Sheets for Web Design ISBN: 978-0-7645-7642-3 1 March 27th, 2005 08:50 AM
Migrate Access XP to SQL Server 2000 Walden Access 1 September 21st, 2003 01:54 AM
Access XP VBA compatibility issues w/ Access 2000 bourgeois02 Access VBA 1 August 19th, 2003 04:14 PM



All times are GMT -4. The time now is 12:57 PM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.