G
Guest
Old timer-develper returning to the drawing board here (from the days of
Access 97)...
Question 1: Does Microsoft still allow (and facilitate) the conversion of
..mde program files into applications that will run outside the Access
environment without any rights or licensing issues?
Question 2: Is it difficult these days to develop small database apps for
MAC users?
Way back in the days of Access 97, converting an Access file into an .mde
file worked to somewhat protect your coding and make it a working
"application".
I read the developers edition for that version many years ago (a great,
comprehensive book, by the way) and it discussed how to go one step farther
by converting the .mde program file into an application that would operate
outside the Access environment. I remember it even discussed how there would
be no copyrights or licensing issues with Microsoft.
Back then, for the studios, I just had them go to the expense of purchasing
a licensed copy of Access for every workstation from which they wanted my app
to run. Now, I'm thinking of developing for many clients outside the studio
walls and I wanted to know if that utility of converting the Access database
still stands in Access 2003.
Thanks for any enlightenment...
(e-mail address removed)
Access 97)...
Question 1: Does Microsoft still allow (and facilitate) the conversion of
..mde program files into applications that will run outside the Access
environment without any rights or licensing issues?
Question 2: Is it difficult these days to develop small database apps for
MAC users?
Way back in the days of Access 97, converting an Access file into an .mde
file worked to somewhat protect your coding and make it a working
"application".
I read the developers edition for that version many years ago (a great,
comprehensive book, by the way) and it discussed how to go one step farther
by converting the .mde program file into an application that would operate
outside the Access environment. I remember it even discussed how there would
be no copyrights or licensing issues with Microsoft.
Back then, for the studios, I just had them go to the expense of purchasing
a licensed copy of Access for every workstation from which they wanted my app
to run. Now, I'm thinking of developing for many clients outside the studio
walls and I wanted to know if that utility of converting the Access database
still stands in Access 2003.
Thanks for any enlightenment...
(e-mail address removed)