Hello,

Someone had told me that there was "a list" of known issues with the Access
Data Project. I like using the ADP at this point, and haven't had any
issues yet, but would like to know what those issues are. Does anyone have
a link or a list of any issues using ADP?

Any help would be appreciated.

Thanks!
Rick

Biggest issue could be that ADP will not be there any more in next Access
release (not upcoming Access2007, it still supports ADP, and likely is the
last version of Access that support ADP).

"Rico" <(E-Mail Removed)> wrote in message
news:gPSYg.154866$R63.111594@pd7urf1no...
> Hello,
>
> Someone had told me that there was "a list" of known issues with the
> Access Data Project. I like using the ADP at this point, and haven't had
> any issues yet, but would like to know what those issues are. Does anyone
> have a link or a list of any issues using ADP?
>
> Any help would be appreciated.
>
> Thanks!
> Rick
>
>

Norman;

you are a liar and a faggot

eat **** ****nut

I do have a list of bugs.. but it's really not that big of a deal.
the biggest thing that ****es me off is this:

a) create a proc in Query Analyzer using this syntax
'create proc mySproc as select * from sysobjects'
b) open this sproc in ADP; make a change and hit save you get
'the parameter is incorrect'

I have more issues.. but it's mainly an annoyance-- you have to ask
other sql developers to not abbreviate 'create procedure' as 'create
proc'

I think that ADP is a wonderful platform. I think that ADP is the most
important product to come from Redmond EVER. More important that
Windows or Excel or Outlook or Internet Explorer.

MDB is completely obsolete; anyone that uses MDB for anything should be
FIRED on the spot. It is completely obsolete and ridiculous. MDB
isn't stable or reliable enough for a single record and a single user.


-Aaron


Norman Yuan wrote:
> Biggest issue could be that ADP will not be there any more in next Access
> release (not upcoming Access2007, it still supports ADP, and likely is the
> last version of Access that support ADP).
>
> "Rico" <(E-Mail Removed)> wrote in message
> news:gPSYg.154866$R63.111594@pd7urf1no...
> > Hello,
> >
> > Someone had told me that there was "a list" of known issues with the
> > Access Data Project. I like using the ADP at this point, and haven't had
> > any issues yet, but would like to know what those issues are. Does anyone
> > have a link or a list of any issues using ADP?
> >
> > Any help would be appreciated.
> >
> > Thanks!
> > Rick
> >
> >

btw Norman; if you want to come out and say those lies to my face; I
would love the opportunity

ADP isn't going away.

MDB _IS_ going away.


-Aaron



Norman Yuan wrote:
> Biggest issue could be that ADP will not be there any more in next Access
> release (not upcoming Access2007, it still supports ADP, and likely is the
> last version of Access that support ADP).
>
> "Rico" <(E-Mail Removed)> wrote in message
> news:gPSYg.154866$R63.111594@pd7urf1no...
> > Hello,
> >
> > Someone had told me that there was "a list" of known issues with the
> > Access Data Project. I like using the ADP at this point, and haven't had
> > any issues yet, but would like to know what those issues are. Does anyone
> > have a link or a list of any issues using ADP?
> >
> > Any help would be appreciated.
> >
> > Thanks!
> > Rick
> >
> >

Access Data Projects are more reliable; more stable; higher
performance-- and easier development than Access MDB.

It woudl be comical to use MDB format in the year 2006.. it has been
obsolete for 7 years now

Ever since Office 2000 shipped in the fall of '99
I remember it; clear as a bell..thinking 'holy **** microsoft is
finally taking access seriously'

-Aaron


(E-Mail Removed) wrote:
> btw Norman; if you want to come out and say those lies to my face; I
> would love the opportunity
>
> ADP isn't going away.
>
> MDB _IS_ going away.
>
>
> -Aaron
>
>
>
> Norman Yuan wrote:
> > Biggest issue could be that ADP will not be there any more in next Access
> > release (not upcoming Access2007, it still supports ADP, and likely is the
> > last version of Access that support ADP).
> >
> > "Rico" <(E-Mail Removed)> wrote in message
> > news:gPSYg.154866$R63.111594@pd7urf1no...
> > > Hello,
> > >
> > > Someone had told me that there was "a list" of known issues with the
> > > Access Data Project. I like using the ADP at this point, and haven't had
> > > any issues yet, but would like to know what those issues are. Does anyone
> > > have a link or a list of any issues using ADP?
> > >
> > > Any help would be appreciated.
> > >
> > > Thanks!
> > > Rick
> > >
> > >

So if I understand correctly, there is no quirky behaviour that will rear
its ugly head as long as the app passes testing and there should be no
surprises for me?

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Norman;
>
> you are a liar and a faggot
>
> eat **** ****nut
>
> I do have a list of bugs.. but it's really not that big of a deal.
> the biggest thing that ****es me off is this:
>
> a) create a proc in Query Analyzer using this syntax
> 'create proc mySproc as select * from sysobjects'
> b) open this sproc in ADP; make a change and hit save you get
> 'the parameter is incorrect'
>
> I have more issues.. but it's mainly an annoyance-- you have to ask
> other sql developers to not abbreviate 'create procedure' as 'create
> proc'
>
> I think that ADP is a wonderful platform. I think that ADP is the most
> important product to come from Redmond EVER. More important that
> Windows or Excel or Outlook or Internet Explorer.
>
> MDB is completely obsolete; anyone that uses MDB for anything should be
> FIRED on the spot. It is completely obsolete and ridiculous. MDB
> isn't stable or reliable enough for a single record and a single user.
>
>
> -Aaron
>
>
> Norman Yuan wrote:
>> Biggest issue could be that ADP will not be there any more in next Access
>> release (not upcoming Access2007, it still supports ADP, and likely is
>> the
>> last version of Access that support ADP).
>>
>> "Rico" <(E-Mail Removed)> wrote in message
>> news:gPSYg.154866$R63.111594@pd7urf1no...
>> > Hello,
>> >
>> > Someone had told me that there was "a list" of known issues with the
>> > Access Data Project. I like using the ADP at this point, and haven't
>> > had
>> > any issues yet, but would like to know what those issues are. Does
>> > anyone
>> > have a link or a list of any issues using ADP?
>> >
>> > Any help would be appreciated.
>> >
>> > Thanks!
>> > Rick
>> >
>> >
>

yeah.. it's a wonderful platform.

I do reccomend runnig Index Tuning Wizard or Database Tuning Advisor in
order to get optimal performance

there might be some hiccups when you go to actually copy this to the
deployment folder.. i think that it works best to copy these files to
the desktop but it's not necessary.

you just will get a warning if 2 people try to open the same file..
it's a bug that drives me crazy; but most Access people are used to
having a different copy of the frontend anyways; so it's not that big
of a deal

just make multiple copies to get around it

-Aaron



Rico wrote:
> So if I understand correctly, there is no quirky behaviour that will rear
> its ugly head as long as the app passes testing and there should be no
> surprises for me?
>
> <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Norman;
> >
> > you are a liar and a faggot
> >
> > eat **** ****nut
> >
> > I do have a list of bugs.. but it's really not that big of a deal.
> > the biggest thing that ****es me off is this:
> >
> > a) create a proc in Query Analyzer using this syntax
> > 'create proc mySproc as select * from sysobjects'
> > b) open this sproc in ADP; make a change and hit save you get
> > 'the parameter is incorrect'
> >
> > I have more issues.. but it's mainly an annoyance-- you have to ask
> > other sql developers to not abbreviate 'create procedure' as 'create
> > proc'
> >
> > I think that ADP is a wonderful platform. I think that ADP is the most
> > important product to come from Redmond EVER. More important that
> > Windows or Excel or Outlook or Internet Explorer.
> >
> > MDB is completely obsolete; anyone that uses MDB for anything should be
> > FIRED on the spot. It is completely obsolete and ridiculous. MDB
> > isn't stable or reliable enough for a single record and a single user.
> >
> >
> > -Aaron
> >
> >
> > Norman Yuan wrote:
> >> Biggest issue could be that ADP will not be there any more in next Access
> >> release (not upcoming Access2007, it still supports ADP, and likely is
> >> the
> >> last version of Access that support ADP).
> >>
> >> "Rico" <(E-Mail Removed)> wrote in message
> >> news:gPSYg.154866$R63.111594@pd7urf1no...
> >> > Hello,
> >> >
> >> > Someone had told me that there was "a list" of known issues with the
> >> > Access Data Project. I like using the ADP at this point, and haven't
> >> > had
> >> > any issues yet, but would like to know what those issues are. Does
> >> > anyone
> >> > have a link or a list of any issues using ADP?
> >> >
> >> > Any help would be appreciated.
> >> >
> >> > Thanks!
> >> > Rick
> >> >
> >> >
> >