We currently use an Access Project (ADP) with a SQL Server 2000
backend. I'm currently making some changes to the project, and am
finding that as the ADP size increases (18/19 MB) I am having more
problems with user testing. Users have Access Runtime 2003 on their
desktops, and they are getting the message that an error has been
encountered, and Access will backup and repair project (which doesn't
stop the fault from happening again).

Tried de-compiling, and importing forms reports etc into blank ADP, but
only converting ADP into ADE seems to solve the problem.

Are there any known problems with using ADE files with Runtime Access
(apart from not allowing design view)?

Will I need to re-test the whole project to make sure the ADE hasn't
stopped any features from working?

Thanks.

Any chance that your users are experimenting problems not because they are
using the ADE version but simply because they are using it more extensively?

They are manu bugs with ADP, so I cannot tell you more about this. However,
two common sources of problems are the use of bit fields bound to a form and
the use of Me.RecordsetClone instead of Me.Recordset.Clone.

For problems strictly related to ADE, the only one I know is using an ADE on
a target machine whose Windows' version and service packs are not strictly
identical to those of the machine where the ADE has been compiled. This can
be easily tested by making an ADE directly on the target machine and see if
the problem persists. Personnally, I do not use MDE & ADE anymore since
many years as I prefer to ask my clients to buy a license of Access for each
user instead of losing innumerous hours of un-billed hours trying to find
why my program doesn't work on a particular machine.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"SteveMc" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We currently use an Access Project (ADP) with a SQL Server 2000
> backend. I'm currently making some changes to the project, and am
> finding that as the ADP size increases (18/19 MB) I am having more
> problems with user testing. Users have Access Runtime 2003 on their
> desktops, and they are getting the message that an error has been
> encountered, and Access will backup and repair project (which doesn't
> stop the fault from happening again).
>
> Tried de-compiling, and importing forms reports etc into blank ADP, but
> only converting ADP into ADE seems to solve the problem.
>
> Are there any known problems with using ADE files with Runtime Access
> (apart from not allowing design view)?
>
> Will I need to re-test the whole project to make sure the ADE hasn't
> stopped any features from working?
>
> Thanks.
>

If forgot to mention that the newsgroup for ADP is m.p.a.adp.sqlserver.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:(E-Mail Removed)...
> Any chance that your users are experimenting problems not because they are
> using the ADE version but simply because they are using it more
> extensively?
>
> They are manu bugs with ADP, so I cannot tell you more about this.
> However, two common sources of problems are the use of bit fields bound to
> a form and the use of Me.RecordsetClone instead of Me.Recordset.Clone.
>
> For problems strictly related to ADE, the only one I know is using an ADE
> on a target machine whose Windows' version and service packs are not
> strictly identical to those of the machine where the ADE has been
> compiled. This can be easily tested by making an ADE directly on the
> target machine and see if the problem persists. Personnally, I do not use
> MDE & ADE anymore since many years as I prefer to ask my clients to buy a
> license of Access for each user instead of losing innumerous hours of
> un-billed hours trying to find why my program doesn't work on a particular
> machine.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "SteveMc" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> We currently use an Access Project (ADP) with a SQL Server 2000
>> backend. I'm currently making some changes to the project, and am
>> finding that as the ADP size increases (18/19 MB) I am having more
>> problems with user testing. Users have Access Runtime 2003 on their
>> desktops, and they are getting the message that an error has been
>> encountered, and Access will backup and repair project (which doesn't
>> stop the fault from happening again).
>>
>> Tried de-compiling, and importing forms reports etc into blank ADP, but
>> only converting ADP into ADE seems to solve the problem.
>>
>> Are there any known problems with using ADE files with Runtime Access
>> (apart from not allowing design view)?
>>
>> Will I need to re-test the whole project to make sure the ADE hasn't
>> stopped any features from working?
>>
>> Thanks.
>>
>
>

Thanks for the reply.

The User (Tester) is having problems with the latest ADP - I've given
her an ADE instead to get round the problem. We haven't used ADEs on
this site before.

Unfortunately we have to use Access Runtime on user machines (for
security and licence reasons). So I won't be able to create the ADE
file on their machine if they have a different Windows version/service
pack. They should all be on Windows XP, but a couple are still on
Windows 2000.

I know what you mean about spending hours trying to find out why
something works on one machine but not another.


Sylvain Lafontaine (fill the blanks, no spam please) wrote:
> Any chance that your users are experimenting problems not because they are
> using the ADE version but simply because they are using it more extensively?
>
> They are manu bugs with ADP, so I cannot tell you more about this. However,
> two common sources of problems are the use of bit fields bound to a form and
> the use of Me.RecordsetClone instead of Me.Recordset.Clone.
>
> For problems strictly related to ADE, the only one I know is using an ADE on
> a target machine whose Windows' version and service packs are not strictly
> identical to those of the machine where the ADE has been compiled. This can
> be easily tested by making an ADE directly on the target machine and see if
> the problem persists. Personnally, I do not use MDE & ADE anymore since
> many years as I prefer to ask my clients to buy a license of Access for each
> user instead of losing innumerous hours of un-billed hours trying to find
> why my program doesn't work on a particular machine.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "SteveMc" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > We currently use an Access Project (ADP) with a SQL Server 2000
> > backend. I'm currently making some changes to the project, and am
> > finding that as the ADP size increases (18/19 MB) I am having more
> > problems with user testing. Users have Access Runtime 2003 on their
> > desktops, and they are getting the message that an error has been
> > encountered, and Access will backup and repair project (which doesn't
> > stop the fault from happening again).
> >
> > Tried de-compiling, and importing forms reports etc into blank ADP, but
> > only converting ADP into ADE seems to solve the problem.
> >
> > Are there any known problems with using ADE files with Runtime Access
> > (apart from not allowing design view)?
> >
> > Will I need to re-test the whole project to make sure the ADE hasn't
> > stopped any features from working?
> >
> > Thanks.
> >

I forgot to mention that using a timestamp column or setting the UniqueTable
and ResyncCommand might help (particularly but not necessarily if you are
using bit fields). Personnally, I don't use timestamp fields very often but
I always take the precaution of setting the UniqueTable and ResyncCommand
properties everywhere.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"SteveMc" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks for the reply.
>
> The User (Tester) is having problems with the latest ADP - I've given
> her an ADE instead to get round the problem. We haven't used ADEs on
> this site before.
>
> Unfortunately we have to use Access Runtime on user machines (for
> security and licence reasons). So I won't be able to create the ADE
> file on their machine if they have a different Windows version/service
> pack. They should all be on Windows XP, but a couple are still on
> Windows 2000.
>
> I know what you mean about spending hours trying to find out why
> something works on one machine but not another.
>
>
> Sylvain Lafontaine (fill the blanks, no spam please) wrote:
>> Any chance that your users are experimenting problems not because they
>> are
>> using the ADE version but simply because they are using it more
>> extensively?
>>
>> They are manu bugs with ADP, so I cannot tell you more about this.
>> However,
>> two common sources of problems are the use of bit fields bound to a form
>> and
>> the use of Me.RecordsetClone instead of Me.Recordset.Clone.
>>
>> For problems strictly related to ADE, the only one I know is using an ADE
>> on
>> a target machine whose Windows' version and service packs are not
>> strictly
>> identical to those of the machine where the ADE has been compiled. This
>> can
>> be easily tested by making an ADE directly on the target machine and see
>> if
>> the problem persists. Personnally, I do not use MDE & ADE anymore since
>> many years as I prefer to ask my clients to buy a license of Access for
>> each
>> user instead of losing innumerous hours of un-billed hours trying to find
>> why my program doesn't work on a particular machine.
>>
>> --
>> Sylvain Lafontaine, ing.
>> MVP - Technologies Virtual-PC
>> E-mail: sylvain aei ca (fill the blanks, no spam please)
>>
>>
>> "SteveMc" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > We currently use an Access Project (ADP) with a SQL Server 2000
>> > backend. I'm currently making some changes to the project, and am
>> > finding that as the ADP size increases (18/19 MB) I am having more
>> > problems with user testing. Users have Access Runtime 2003 on their
>> > desktops, and they are getting the message that an error has been
>> > encountered, and Access will backup and repair project (which doesn't
>> > stop the fault from happening again).
>> >
>> > Tried de-compiling, and importing forms reports etc into blank ADP, but
>> > only converting ADP into ADE seems to solve the problem.
>> >
>> > Are there any known problems with using ADE files with Runtime Access
>> > (apart from not allowing design view)?
>> >
>> > Will I need to re-test the whole project to make sure the ADE hasn't
>> > stopped any features from working?
>> >
>> > Thanks.
>> >
>

how many pictures you got in that ADP LoL

18/19 mb is completely unacceptable; it's not code

I've built hundreds and hundreds of forms and reports and never gotten
over 10 mb

-Aaron


SteveMc wrote:
> We currently use an Access Project (ADP) with a SQL Server 2000
> backend. I'm currently making some changes to the project, and am
> finding that as the ADP size increases (18/19 MB) I am having more
> problems with user testing. Users have Access Runtime 2003 on their
> desktops, and they are getting the message that an error has been
> encountered, and Access will backup and repair project (which doesn't
> stop the fault from happening again).
>
> Tried de-compiling, and importing forms reports etc into blank ADP, but
> only converting ADP into ADE seems to solve the problem.
>
> Are there any known problems with using ADE files with Runtime Access
> (apart from not allowing design view)?
>
> Will I need to re-test the whole project to make sure the ADE hasn't
> stopped any features from working?
>
> Thanks.

No pictures in ADP - just 280 forms, 170 reports, and 11 modules.

Quite a lot of References in code, which will be adding to size.


(E-Mail Removed) wrote:
> how many pictures you got in that ADP LoL
>
> 18/19 mb is completely unacceptable; it's not code
>
> I've built hundreds and hundreds of forms and reports and never gotten
> over 10 mb
>
> -Aaron
>
>
> SteveMc wrote:
> > We currently use an Access Project (ADP) with a SQL Server 2000
> > backend. I'm currently making some changes to the project, and am
> > finding that as the ADP size increases (18/19 MB) I am having more
> > problems with user testing. Users have Access Runtime 2003 on their
> > desktops, and they are getting the message that an error has been
> > encountered, and Access will backup and repair project (which doesn't
> > stop the fault from happening again).
> >
> > Tried de-compiling, and importing forms reports etc into blank ADP, but
> > only converting ADP into ADE seems to solve the problem.
> >
> > Are there any known problems with using ADE files with Runtime Access
> > (apart from not allowing design view)?
> >
> > Will I need to re-test the whole project to make sure the ADE hasn't
> > stopped any features from working?
> >
> > Thanks.

friggin wow dude

im impressed and I want a job

(E-Mail Removed) catch me on instant messenger

-Aaron


SteveMc wrote:
> No pictures in ADP - just 280 forms, 170 reports, and 11 modules.
>
> Quite a lot of References in code, which will be adding to size.
>
>
> (E-Mail Removed) wrote:
> > how many pictures you got in that ADP LoL
> >
> > 18/19 mb is completely unacceptable; it's not code
> >
> > I've built hundreds and hundreds of forms and reports and never gotten
> > over 10 mb
> >
> > -Aaron
> >
> >
> > SteveMc wrote:
> > > We currently use an Access Project (ADP) with a SQL Server 2000
> > > backend. I'm currently mak
ing some changes to the project, and am
> > > finding that as the ADP size increases (18/19 MB) I am having more
> > > problems with user testing. Users have Access Runtime 2003 on their
> > > desktops, and they are getting the message that an error has been
> > > encountered, and Access will backup and repair project (which doesn't
> > > stop the fault from happening again).
> > >
> > > Tried de-compiling, and importing forms reports etc into blank ADP, but
> > > only converting ADP into ADE seems to solve the problem.
> > >
> > > Are there any known problems with using ADE files with Runtime Access
> > > (apart from not allowing design view)?
> > >
> > > Will I need to re-test the whole project to make sure the ADE hasn't
> > > stopped any features from working?
> > >
> > > Thanks.

Not here you don't! It's not worth the headache...


(E-Mail Removed) wrote:
> friggin wow dude
>
> im impressed and I want a job
>
> (E-Mail Removed) catch me on instant messenger
>
> -Aaron
>
>
> SteveMc wrote:
> > No pictures in ADP - just 280 forms, 170 reports, and 11 modules.
> >
> > Quite a lot of References in code, which will be adding to size.
> >
> >
> > (E-Mail Removed) wrote:
> > > how many pictures you got in that ADP LoL
> > >
> > > 18/19 mb is completely unacceptable; it's not code
> > >
> > > I've built hundreds and hundreds of forms and reports and never gotten
> > > over 10 mb
> > >
> > > -Aaron
> > >
> > >
> > > SteveMc wrote:
> > > > We currently use an Access Project (ADP) with a SQL Server 2000
> > > > backend. I'm currently mak
> ing some changes to the project, and am
> > > > finding that as the ADP size increases (18/19 MB) I am having more
> > > > problems with user testing. Users have Access Runtime 2003 on their
> > > > desktops, and they are getting the message that an error has been
> > > > encountered, and Access will backup and repair project (which doesn't
> > > > stop the fault from happening again).
> > > >
> > > > Tried de-compiling, and importing forms reports etc into blank ADP, but
> > > > only converting ADP into ADE seems to solve the problem.
> > > >
> > > > Are there any known problems with using ADE files with Runtime Access
> > > > (apart from not allowing design view)?
> > > >
> > > > Will I need to re-test the whole project to make sure the ADE hasn't
> > > > stopped any features from working?
> > > >
> > > > Thanks.

well I haven't found many people that have worked on more complex ADP
than I have

and I really honestly think that it's the most powerful, more important
platform to come out of Redmond EVER.

and Microsoft doesn't take it seriously.

Have you considered making a white paper about how much ADP has helped
your company?

I just want to motivate MS to take it seriously; I think that the fat
lazy retards in redmond that failed to market ADP for the past decade
should be fired.

-Aaron



SteveMc wrote:
> Not here you don't! It's not worth the headache...
>
>
> (E-Mail Removed) wrote:
> > friggin wow dude
> >
> > im impressed and I want a job
> >
> > (E-Mail Removed) catch me on instant messenger
> >
> > -Aaron
> >
> >
> > SteveMc wrote:
> > > No pictures in ADP - just 280 forms, 170 reports, and 11 modules.
> > >
> > > Quite a lot of References in code, which will be adding to size.
> > >
> > >
> > > (E-Mail Removed) wrote:
> > > > how many pictures you got in that ADP LoL
> > > >
> > > > 18/19 mb is completely unacceptable; it's not code
> > > >
> > > > I've built hundreds and hundreds of forms and reports and never gotten
> > > > over 10 mb
> > > >
> > > > -Aaron
> > > >
> > > >
> > > > SteveMc wrote:
> > > > > We currently use an Access Project (ADP) with a SQL Server 2000
> > > > > backend. I'm currently mak
> > ing some changes to the project, and am
> > > > > finding that as the ADP size increases (18/19 MB) I am having more
> > > > > problems with user testing. Users have Access Runtime 2003 on their
> > > > > desktops, and they are getting the message that an error has been
> > > > > encountered, and Access will backup and repair project (which doesn't
> > > > > stop the fault from happening again).
> > > > >
> > > > > Tried de-compiling, and importing forms reports etc into blank ADP, but
> > > > > only converting ADP into ADE seems to solve the problem.
> > > > >
> > > > > Are there any known problems with using ADE files with Runtime Access
> > > > > (apart from not allowing design view)?
> > > > >
> > > > > Will I need to re-test the whole project to make sure the ADE hasn't
> > > > > stopped any features from working?
> > > > >
> > > > > Thanks.