Limitations using Developer
- From: "cottage6" <cottage6@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 12 Aug 2005 07:14:02 -0700
My company is in the middle of a conversion from Lotus products to MS Office.
I need to rewrite an old complicated Approach file to Access (Access 2000).
I'm not very advanced in my Access knowledge yet and have only used the
packaging wizard (XP Developer) once to get a database to a user who didn't
have Access. If I remember correctly, after the database got to the user
there were some things she couldn't do that I was able to when I created the
database. Sorry I can't quite remember what they were; it's been awhile.
Anyway before I start the rewrite on this I'd like to know what I can't
expect a user to have in a database using the packaging wizard, versus
installing Access on the user's PC. It's always a possibility I did
something wrong to begin with. Any feedback would be great. TIA.
.
- Follow-Ups:
- Re: Limitations using Developer
- From: Chris Mills
- Re: Limitations using Developer
- Prev by Date: Re: You don't have the license required to use this ActiveX control
- Next by Date: Finding a single value in a table
- Previous by thread: You don't have the license required to use this ActiveX control
- Next by thread: Re: Limitations using Developer
- Index(es):
Relevant Pages
|
Loading