VBA, Make adp table behave like linked mdb table.

Make adp table behave like linked mdb table.

Author	Message
Manuel Lope #1 / 13	Make adp table behave like linked mdb table. Small question, but still a question: What is the best way of getting a table in an Access adp file to behave like a linked table in an mdb file? I mean in this respect: Table A has 500,000 rows in order from 1 to 500,000 (primary key order). In an mdb file (linked to the same backend that the adp is using), the user opens Table A, sees records 1-100 (in order from 1 at the top to 100 at the bottom), presses the move last button, and access immediately jumps to records 499,900 to 500,000 (in order from 499,900 at the top to 500,000 at bottom), without loading all the intermediary records before jumping (and while still being able to see the records in between if he so chooses). In an adp file, user opens Table A, sees records 1-100, and can't get to records 499,900 to 500,000 without actually loading all the intermediary records (takes a long time). I know one can probably custom code all of this, but I thought there must be an easier way to duplicate the behavior of the mdb file in the adp file. Or what is the easiest way to do this? Note all the things that have to duplicated: potential access to the whole table, primary key order from top to bottom, and the quick jump to the end, i.e. I need a close imitation of the mdb file behavior.
Wed, 16 Apr 2003 14:30:11 GMT

Joe Fallo #2 / 13	Make adp table behave like linked mdb table. "I know one can probably custom code all of this, but I thought there must be an easier way to duplicate the behavior of the mdb file " What makes you think that re-writing the Jet engine is 'easy'? I suggest using forms and code to jump to small portions of the table. Do not use the table directly. -- Joe Access MVP Check out Dev Ashish's web site for answers to common questions http://www.mvps.org/access/ Quote: > Small question, but still a question: What is the best way of getting a > table in an Access adp file to behave like a linked table in an mdb file? > I mean in this respect: > Table A has 500,000 rows in order from 1 to 500,000 (primary key order). > In an mdb file (linked to the same backend that the adp is using), the user > opens Table A, sees records 1-100 (in order from 1 at the top to 100 at the > bottom), presses the move last button, and access immediately jumps to > records 499,900 to 500,000 (in order from 499,900 at the top to 500,000 at > bottom), without loading all the intermediary records before jumping (and > while still being able to see the records in between if he so chooses). > In an adp file, user opens Table A, sees records 1-100, and can't get to > records 499,900 to 500,000 without actually loading all the intermediary > records (takes a long time). > I know one can probably custom code all of this, but I thought there must be > an easier way to duplicate the behavior of the mdb file in the adp file. Or > what is the easiest way to do this? > Note all the things that have to duplicated: potential access to the whole > table, primary key order from top to bottom, and the quick jump to the end, > i.e. I need a close imitation of the mdb file behavior.
Fri, 18 Apr 2003 07:03:02 GMT

Manuel Lope #3 / 13	Make adp table behave like linked mdb table. I was looking around for some easier way which doesn't exist. The user NEEDS to be able to browse the whole thing, or to get a close imitation of that. Essentially, if I went the adp route, I wouldn't be rewriting jet but, along the lines of what you said, creating a form with a datasheet that opens pulling the last n records and that has a custom back navigation button that pulls the previous n records. Anyway, the whole thing would still be slower and much less useful than just having the whole table there in the first place. But Michael Kaplan makes a strong case for using linked tables in mdb to sql server instead of adps. I could avoid this code then, since it's only 3 or 4 seconds to open the whole table that way (odbc) instead of the adp way (60+ secs). But I'm still weighing the pro's and con's. I could try sticking with jet mdbs on the backend for another year and see how this improves with access 10. Quote: > "I know one can probably custom code all of this, but I thought there must > be > an easier way to duplicate the behavior of the mdb file " > What makes you think that re-writing the Jet engine is 'easy'? > I suggest using forms and code to jump to small portions of the table. > Do not use the table directly. > -- > Joe > Access MVP > Check out Dev Ashish's web site for answers to common questions > http://www.mvps.org/access/ > > Small question, but still a question: What is the best way of getting a > > table in an Access adp file to behave like a linked table in an mdb file? > > I mean in this respect: > > Table A has 500,000 rows in order from 1 to 500,000 (primary key order). > > In an mdb file (linked to the same backend that the adp is using), the > user > > opens Table A, sees records 1-100 (in order from 1 at the top to 100 at > the > > bottom), presses the move last button, and access immediately jumps to > > records 499,900 to 500,000 (in order from 499,900 at the top to 500,000 at > > bottom), without loading all the intermediary records before jumping (and > > while still being able to see the records in between if he so chooses). > > In an adp file, user opens Table A, sees records 1-100, and can't get to > > records 499,900 to 500,000 without actually loading all the intermediary > > records (takes a long time). > > I know one can probably custom code all of this, but I thought there must > be > > an easier way to duplicate the behavior of the mdb file in the adp file. > Or > > what is the easiest way to do this? > > Note all the things that have to duplicated: potential access to the whole > > table, primary key order from top to bottom, and the quick jump to the > end, > > i.e. I need a close imitation of the mdb file behavior.
Fri, 18 Apr 2003 08:27:32 GMT

Joe Fallo #4 / 13	Make adp table behave like linked mdb table. You have given a very good response to this. Agreeing with Michka is a pretty easy thing to do so consider it done. I use linked SQL Server tables in mdb's all the time and am quite happy with Jet's ability to manipulate them. -- Joe Access MVP Check out Dev Ashish's web site for answers to common questions http://www.mvps.org/access/ Quote: > I was looking around for some easier way which doesn't exist. The user > NEEDS to be able to browse the whole thing, or to get a close imitation of > that. Essentially, if I went the adp route, I wouldn't be rewriting jet > but, along the lines of what you said, creating a form with a datasheet that > opens pulling the last n records and that has a custom back navigation > button that pulls the previous n records. Anyway, the whole thing would > still be slower and much less useful than just having the whole table there > in the first place. > But Michael Kaplan makes a strong case for using linked tables in mdb to sql > server instead of adps. I could avoid this code then, since it's only 3 or > 4 seconds to open the whole table that way (odbc) instead of the adp way > (60+ secs). But I'm still weighing the pro's and con's. I could try > sticking with jet mdbs on the backend for another year and see how this > improves with access 10. > > "I know one can probably custom code all of this, but I thought there must > > be > > an easier way to duplicate the behavior of the mdb file " > > What makes you think that re-writing the Jet engine is 'easy'? > > I suggest using forms and code to jump to small portions of the table. > > Do not use the table directly. > > -- > > Joe > > Access MVP > > Check out Dev Ashish's web site for answers to common questions > > http://www.mvps.org/access/ > > > Small question, but still a question: What is the best way of getting a > > > table in an Access adp file to behave like a linked table in an mdb > file? > > > I mean in this respect: > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key order). > > > In an mdb file (linked to the same backend that the adp is using), the > > user > > > opens Table A, sees records 1-100 (in order from 1 at the top to 100 at > > the > > > bottom), presses the move last button, and access immediately jumps to > > > records 499,900 to 500,000 (in order from 499,900 at the top to 500,000 > at > > > bottom), without loading all the intermediary records before jumping > (and > > > while still being able to see the records in between if he so chooses). > > > In an adp file, user opens Table A, sees records 1-100, and can't get to > > > records 499,900 to 500,000 without actually loading all the intermediary > > > records (takes a long time). > > > I know one can probably custom code all of this, but I thought there > must > > be > > > an easier way to duplicate the behavior of the mdb file in the adp file. > > Or > > > what is the easiest way to do this? > > > Note all the things that have to duplicated: potential access to the > whole > > > table, primary key order from top to bottom, and the quick jump to the > > end, > > > i.e. I need a close imitation of the mdb file behavior.
Fri, 18 Apr 2003 11:38:16 GMT

Paul Browe #5 / 13	Make adp table behave like linked mdb table. Access 10? I thought Access 2000 was the end of the line. -- Paul Brower http://www.browerconsulting.com DO NOT EMAIL ME Quote: > I was looking around for some easier way which doesn't exist. The user > NEEDS to be able to browse the whole thing, or to get a close imitation of > that. Essentially, if I went the adp route, I wouldn't be rewriting jet > but, along the lines of what you said, creating a form with a datasheet that > opens pulling the last n records and that has a custom back navigation > button that pulls the previous n records. Anyway, the whole thing would > still be slower and much less useful than just having the whole table there > in the first place. > But Michael Kaplan makes a strong case for using linked tables in mdb to sql > server instead of adps. I could avoid this code then, since it's only 3 or > 4 seconds to open the whole table that way (odbc) instead of the adp way > (60+ secs). But I'm still weighing the pro's and con's. I could try > sticking with jet mdbs on the backend for another year and see how this > improves with access 10. > > "I know one can probably custom code all of this, but I thought there must > > be > > an easier way to duplicate the behavior of the mdb file " > > What makes you think that re-writing the Jet engine is 'easy'? > > I suggest using forms and code to jump to small portions of the table. > > Do not use the table directly. > > -- > > Joe > > Access MVP > > Check out Dev Ashish's web site for answers to common questions > > http://www.mvps.org/access/ > > > Small question, but still a question: What is the best way of getting a > > > table in an Access adp file to behave like a linked table in an mdb > file? > > > I mean in this respect: > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key order). > > > In an mdb file (linked to the same backend that the adp is using), the > > user > > > opens Table A, sees records 1-100 (in order from 1 at the top to 100 at > > the > > > bottom), presses the move last button, and access immediately jumps to > > > records 499,900 to 500,000 (in order from 499,900 at the top to 500,000 > at > > > bottom), without loading all the intermediary records before jumping > (and > > > while still being able to see the records in between if he so chooses). > > > In an adp file, user opens Table A, sees records 1-100, and can't get to > > > records 499,900 to 500,000 without actually loading all the intermediary > > > records (takes a long time). > > > I know one can probably custom code all of this, but I thought there > must > > be > > > an easier way to duplicate the behavior of the mdb file in the adp file. > > Or > > > what is the easiest way to do this? > > > Note all the things that have to duplicated: potential access to the > whole > > > table, primary key order from top to bottom, and the quick jump to the > > end, > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 01:23:42 GMT

michk #6 / 13	Make adp table behave like linked mdb table. Huh? What are you talking about??? -- MichKa a new book on internationalization in VB at http://www.i18nWithVB.com/ Quote: > Access 10? I thought Access 2000 was the end of the line. > -- > Paul Brower > http://www.browerconsulting.com > DO NOT EMAIL ME > > I was looking around for some easier way which doesn't exist. The user > > NEEDS to be able to browse the whole thing, or to get a close imitation of > > that. Essentially, if I went the adp route, I wouldn't be rewriting jet > > but, along the lines of what you said, creating a form with a datasheet > that > > opens pulling the last n records and that has a custom back navigation > > button that pulls the previous n records. Anyway, the whole thing would > > still be slower and much less useful than just having the whole table > there > > in the first place. > > But Michael Kaplan makes a strong case for using linked tables in mdb to > sql > > server instead of adps. I could avoid this code then, since it's only 3 > or > > 4 seconds to open the whole table that way (odbc) instead of the adp way > > (60+ secs). But I'm still weighing the pro's and con's. I could try > > sticking with jet mdbs on the backend for another year and see how this > > improves with access 10. > > > "I know one can probably custom code all of this, but I thought there > must > > > be > > > an easier way to duplicate the behavior of the mdb file " > > > What makes you think that re-writing the Jet engine is 'easy'? > > > I suggest using forms and code to jump to small portions of the table. > > > Do not use the table directly. > > > -- > > > Joe > > > Access MVP > > > Check out Dev Ashish's web site for answers to common questions > > > http://www.mvps.org/access/ > > > > Small question, but still a question: What is the best way of getting > a > > > > table in an Access adp file to behave like a linked table in an mdb > > file? > > > > I mean in this respect: > > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key > order). > > > > In an mdb file (linked to the same backend that the adp is using), the > > > user > > > > opens Table A, sees records 1-100 (in order from 1 at the top to 100 > at > > > the > > > > bottom), presses the move last button, and access immediately jumps to > > > > records 499,900 to 500,000 (in order from 499,900 at the top to > 500,000 > > at > > > > bottom), without loading all the intermediary records before jumping > > (and > > > > while still being able to see the records in between if he so > chooses). > > > > In an adp file, user opens Table A, sees records 1-100, and can't get > to > > > > records 499,900 to 500,000 without actually loading all the > intermediary > > > > records (takes a long time). > > > > I know one can probably custom code all of this, but I thought there > > must > > > be > > > > an easier way to duplicate the behavior of the mdb file in the adp > file. > > > Or > > > > what is the easiest way to do this? > > > > Note all the things that have to duplicated: potential access to the > > whole > > > > table, primary key order from top to bottom, and the quick jump to the > > > end, > > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 01:47:30 GMT

Paul Browe #7 / 13	Make adp table behave like linked mdb table. Not trying to start any rumors here ... I thought I'd heard somewhere that it wouldn't be continued. Michael, if you haven't heard anything, I must be mistaken. My apologies. -- Paul Brower http://www.browerconsulting.com DO NOT EMAIL ME Quote: > Huh? What are you talking about??? > -- > MichKa > a new book on internationalization in VB at > http://www.i18nWithVB.com/ > > Access 10? I thought Access 2000 was the end of the line. > > -- > > Paul Brower > > http://www.browerconsulting.com > > DO NOT EMAIL ME > > > I was looking around for some easier way which doesn't exist. The user > > > NEEDS to be able to browse the whole thing, or to get a close imitation > of > > > that. Essentially, if I went the adp route, I wouldn't be rewriting jet > > > but, along the lines of what you said, creating a form with a datasheet > > that > > > opens pulling the last n records and that has a custom back navigation > > > button that pulls the previous n records. Anyway, the whole thing would > > > still be slower and much less useful than just having the whole table > > there > > > in the first place. > > > But Michael Kaplan makes a strong case for using linked tables in mdb to > > sql > > > server instead of adps. I could avoid this code then, since it's only 3 > > or > > > 4 seconds to open the whole table that way (odbc) instead of the adp way > > > (60+ secs). But I'm still weighing the pro's and con's. I could try > > > sticking with jet mdbs on the backend for another year and see how this > > > improves with access 10. > > > > "I know one can probably custom code all of this, but I thought there > > must > > > > be > > > > an easier way to duplicate the behavior of the mdb file " > > > > What makes you think that re-writing the Jet engine is 'easy'? > > > > I suggest using forms and code to jump to small portions of the table. > > > > Do not use the table directly. > > > > -- > > > > Joe > > > > Access MVP > > > > Check out Dev Ashish's web site for answers to common questions > > > > http://www.mvps.org/access/ > > > > > Small question, but still a question: What is the best way of > getting > > a > > > > > table in an Access adp file to behave like a linked table in an mdb > > > file? > > > > > I mean in this respect: > > > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key > > order). > > > > > In an mdb file (linked to the same backend that the adp is using), > the > > > > user > > > > > opens Table A, sees records 1-100 (in order from 1 at the top to 100 > > at > > > > the > > > > > bottom), presses the move last button, and access immediately jumps > to > > > > > records 499,900 to 500,000 (in order from 499,900 at the top to > > 500,000 > > > at > > > > > bottom), without loading all the intermediary records before jumping > > > (and > > > > > while still being able to see the records in between if he so > > chooses). > > > > > In an adp file, user opens Table A, sees records 1-100, and can't > get > > to > > > > > records 499,900 to 500,000 without actually loading all the > > intermediary > > > > > records (takes a long time). > > > > > I know one can probably custom code all of this, but I thought there > > > must > > > > be > > > > > an easier way to duplicate the behavior of the mdb file in the adp > > file. > > > > Or > > > > > what is the easiest way to do this? > > > > > Note all the things that have to duplicated: potential access to the > > > whole > > > > > table, primary key order from top to bottom, and the quick jump to > the > > > > end, > > > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 07:58:42 GMT

michk #8 / 13	Make adp table behave like linked mdb table. Access 10 exists and Beta 2 is gonna be out any day now. How can it be the end of the line if they are in Beta 2 of the next version? -- MichKa a new book on internationalization in VB at http://www.i18nWithVB.com/ Quote: > Not trying to start any rumors here ... I thought I'd heard somewhere that > it wouldn't be continued. Michael, if you haven't heard anything, I must be > mistaken. My apologies. > -- > Paul Brower > http://www.browerconsulting.com > DO NOT EMAIL ME wrote > > Huh? What are you talking about??? > > -- > > MichKa > > a new book on internationalization in VB at > > http://www.i18nWithVB.com/ > > > Access 10? I thought Access 2000 was the end of the line. > > > -- > > > Paul Brower > > > http://www.browerconsulting.com > > > DO NOT EMAIL ME > > > > I was looking around for some easier way which doesn't exist. The > user > > > > NEEDS to be able to browse the whole thing, or to get a close > imitation > > of > > > > that. Essentially, if I went the adp route, I wouldn't be rewriting > jet > > > > but, along the lines of what you said, creating a form with a > datasheet > > > that > > > > opens pulling the last n records and that has a custom back navigation > > > > button that pulls the previous n records. Anyway, the whole thing > would > > > > still be slower and much less useful than just having the whole table > > > there > > > > in the first place. > > > > But Michael Kaplan makes a strong case for using linked tables in mdb > to > > > sql > > > > server instead of adps. I could avoid this code then, since it's only > 3 > > > or > > > > 4 seconds to open the whole table that way (odbc) instead of the adp > way > > > > (60+ secs). But I'm still weighing the pro's and con's. I could try > > > > sticking with jet mdbs on the backend for another year and see how > this > > > > improves with access 10. > > > > > "I know one can probably custom code all of this, but I thought > there > > > must > > > > > be > > > > > an easier way to duplicate the behavior of the mdb file " > > > > > What makes you think that re-writing the Jet engine is 'easy'? > > > > > I suggest using forms and code to jump to small portions of the > table. > > > > > Do not use the table directly. > > > > > -- > > > > > Joe > > > > > Access MVP > > > > > Check out Dev Ashish's web site for answers to common questions > > > > > http://www.mvps.org/access/ > > > > > > Small question, but still a question: What is the best way of > > getting > > > a > > > > > > table in an Access adp file to behave like a linked table in an > mdb > > > > file? > > > > > > I mean in this respect: > > > > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key > > > order). > > > > > > In an mdb file (linked to the same backend that the adp is using), > > the > > > > > user > > > > > > opens Table A, sees records 1-100 (in order from 1 at the top to > 100 > > > at > > > > > the > > > > > > bottom), presses the move last button, and access immediately > jumps > > to > > > > > > records 499,900 to 500,000 (in order from 499,900 at the top to > > > 500,000 > > > > at > > > > > > bottom), without loading all the intermediary records before > jumping > > > > (and > > > > > > while still being able to see the records in between if he so > > > chooses). > > > > > > In an adp file, user opens Table A, sees records 1-100, and can't > > get > > > to > > > > > > records 499,900 to 500,000 without actually loading all the > > > intermediary > > > > > > records (takes a long time). > > > > > > I know one can probably custom code all of this, but I thought > there > > > > must > > > > > be > > > > > > an easier way to duplicate the behavior of the mdb file in the adp > > > file. > > > > > Or > > > > > > what is the easiest way to do this? > > > > > > Note all the things that have to duplicated: potential access to > the > > > > whole > > > > > > table, primary key order from top to bottom, and the quick jump to > > the > > > > > end, > > > > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 08:56:49 GMT

Tibor Karasz #9 / 13	Make adp table behave like linked mdb table. Perhaps Paul had heard about "phasing out - as a very long term objective" the JET engine? -- Tibor Karaszi, SQL Server MVP Please reply to the newsgroup only, not by email. FAQ at: http://www.sqlserverfaq.com Quote: > Access 10 exists and Beta 2 is gonna be out any day now. How can it be the > end of the line if they are in Beta 2 of the next version? > -- > MichKa > a new book on internationalization in VB at > http://www.i18nWithVB.com/ > > Not trying to start any rumors here ... I thought I'd heard somewhere that > > it wouldn't be continued. Michael, if you haven't heard anything, I must > be > > mistaken. My apologies. > > -- > > Paul Brower > > http://www.browerconsulting.com > > DO NOT EMAIL ME > wrote > > > Huh? What are you talking about??? > > > -- > > > MichKa > > > a new book on internationalization in VB at > > > http://www.i18nWithVB.com/ > > > > Access 10? I thought Access 2000 was the end of the line. > > > > -- > > > > Paul Brower > > > > http://www.browerconsulting.com > > > > DO NOT EMAIL ME > > > > > I was looking around for some easier way which doesn't exist. The > > user > > > > > NEEDS to be able to browse the whole thing, or to get a close > > imitation > > > of > > > > > that. Essentially, if I went the adp route, I wouldn't be rewriting > > jet > > > > > but, along the lines of what you said, creating a form with a > > datasheet > > > > that > > > > > opens pulling the last n records and that has a custom back > navigation > > > > > button that pulls the previous n records. Anyway, the whole thing > > would > > > > > still be slower and much less useful than just having the whole > table > > > > there > > > > > in the first place. > > > > > But Michael Kaplan makes a strong case for using linked tables in > mdb > > to > > > > sql > > > > > server instead of adps. I could avoid this code then, since it's > only > > 3 > > > > or > > > > > 4 seconds to open the whole table that way (odbc) instead of the adp > > way > > > > > (60+ secs). But I'm still weighing the pro's and con's. I could > try > > > > > sticking with jet mdbs on the backend for another year and see how > > this > > > > > improves with access 10. > > > > > > "I know one can probably custom code all of this, but I thought > > there > > > > must > > > > > > be > > > > > > an easier way to duplicate the behavior of the mdb file " > > > > > > What makes you think that re-writing the Jet engine is 'easy'? > > > > > > I suggest using forms and code to jump to small portions of the > > table. > > > > > > Do not use the table directly. > > > > > > -- > > > > > > Joe > > > > > > Access MVP > > > > > > Check out Dev Ashish's web site for answers to common questions > > > > > > http://www.mvps.org/access/ > > > > > > > Small question, but still a question: What is the best way of > > > getting > > > > a > > > > > > > table in an Access adp file to behave like a linked table in an > > mdb > > > > > file? > > > > > > > I mean in this respect: > > > > > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key > > > > order). > > > > > > > In an mdb file (linked to the same backend that the adp is > using), > > > the > > > > > > user > > > > > > > opens Table A, sees records 1-100 (in order from 1 at the top to > > 100 > > > > at > > > > > > the > > > > > > > bottom), presses the move last button, and access immediately > > jumps > > > to > > > > > > > records 499,900 to 500,000 (in order from 499,900 at the top to > > > > 500,000 > > > > > at > > > > > > > bottom), without loading all the intermediary records before > > jumping > > > > > (and > > > > > > > while still being able to see the records in between if he so > > > > chooses). > > > > > > > In an adp file, user opens Table A, sees records 1-100, and > can't > > > get > > > > to > > > > > > > records 499,900 to 500,000 without actually loading all the > > > > intermediary > > > > > > > records (takes a long time). > > > > > > > I know one can probably custom code all of this, but I thought > > there > > > > > must > > > > > > be > > > > > > > an easier way to duplicate the behavior of the mdb file in the > adp > > > > file. > > > > > > Or > > > > > > > what is the easiest way to do this? > > > > > > > Note all the things that have to duplicated: potential access to > > the > > > > > whole > > > > > > > table, primary key order from top to bottom, and the quick jump > to > > > the > > > > > > end, > > > > > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 15:37:49 GMT

Paul Browe #10 / 13	Make adp table behave like linked mdb table. Well, you see what happens when I've been doing only VB stuff for about 6 months :-) Since it was brought up, does Access 10 use Jet? -- Paul Brower http://www.browerconsulting.com DO NOT EMAIL ME Quote: > Access 10 exists and Beta 2 is gonna be out any day now. How can it be the > end of the line if they are in Beta 2 of the next version? > -- > MichKa > a new book on internationalization in VB at > http://www.i18nWithVB.com/ > > Not trying to start any rumors here ... I thought I'd heard somewhere that > > it wouldn't be continued. Michael, if you haven't heard anything, I must > be > > mistaken. My apologies. > > -- > > Paul Brower > > http://www.browerconsulting.com > > DO NOT EMAIL ME > wrote > > > Huh? What are you talking about??? > > > -- > > > MichKa > > > a new book on internationalization in VB at > > > http://www.i18nWithVB.com/ > > > > Access 10? I thought Access 2000 was the end of the line. > > > > -- > > > > Paul Brower > > > > http://www.browerconsulting.com > > > > DO NOT EMAIL ME > > > > > I was looking around for some easier way which doesn't exist. The > > user > > > > > NEEDS to be able to browse the whole thing, or to get a close > > imitation > > > of > > > > > that. Essentially, if I went the adp route, I wouldn't be rewriting > > jet > > > > > but, along the lines of what you said, creating a form with a > > datasheet > > > > that > > > > > opens pulling the last n records and that has a custom back > navigation > > > > > button that pulls the previous n records. Anyway, the whole thing > > would > > > > > still be slower and much less useful than just having the whole > table > > > > there > > > > > in the first place. > > > > > But Michael Kaplan makes a strong case for using linked tables in > mdb > > to > > > > sql > > > > > server instead of adps. I could avoid this code then, since it's > only > > 3 > > > > or > > > > > 4 seconds to open the whole table that way (odbc) instead of the adp > > way > > > > > (60+ secs). But I'm still weighing the pro's and con's. I could > try > > > > > sticking with jet mdbs on the backend for another year and see how > > this > > > > > improves with access 10. > > > > > > "I know one can probably custom code all of this, but I thought > > there > > > > must > > > > > > be > > > > > > an easier way to duplicate the behavior of the mdb file " > > > > > > What makes you think that re-writing the Jet engine is 'easy'? > > > > > > I suggest using forms and code to jump to small portions of the > > table. > > > > > > Do not use the table directly. > > > > > > -- > > > > > > Joe > > > > > > Access MVP > > > > > > Check out Dev Ashish's web site for answers to common questions > > > > > > http://www.mvps.org/access/ message > > > > > > > Small question, but still a question: What is the best way of > > > getting > > > > a > > > > > > > table in an Access adp file to behave like a linked table in an > > mdb > > > > > file? > > > > > > > I mean in this respect: > > > > > > > Table A has 500,000 rows in order from 1 to 500,000 (primary key > > > > order). > > > > > > > In an mdb file (linked to the same backend that the adp is > using), > > > the > > > > > > user > > > > > > > opens Table A, sees records 1-100 (in order from 1 at the top to > > 100 > > > > at > > > > > > the > > > > > > > bottom), presses the move last button, and access immediately > > jumps > > > to > > > > > > > records 499,900 to 500,000 (in order from 499,900 at the top to > > > > 500,000 > > > > > at > > > > > > > bottom), without loading all the intermediary records before > > jumping > > > > > (and > > > > > > > while still being able to see the records in between if he so > > > > chooses). > > > > > > > In an adp file, user opens Table A, sees records 1-100, and > can't > > > get > > > > to > > > > > > > records 499,900 to 500,000 without actually loading all the > > > > intermediary > > > > > > > records (takes a long time). > > > > > > > I know one can probably custom code all of this, but I thought > > there > > > > > must > > > > > > be > > > > > > > an easier way to duplicate the behavior of the mdb file in the > adp > > > > file. > > > > > > Or > > > > > > > what is the easiest way to do this? > > > > > > > Note all the things that have to duplicated: potential access to > > the > > > > > whole > > > > > > > table, primary key order from top to bottom, and the quick jump > to > > > the > > > > > > end, > > > > > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 23:38:03 GMT

michk #11 / 13	Make adp table behave like linked mdb table. Yes, and its still the default for new files. -- MichKa a new book on internationalization in VB at http://www.i18nWithVB.com/ Quote: > Well, you see what happens when I've been doing only VB stuff for about 6 > months :-) Since it was brought up, does Access 10 use Jet? > -- > Paul Brower > http://www.browerconsulting.com > DO NOT EMAIL ME wrote > > Access 10 exists and Beta 2 is gonna be out any day now. How can it be > the > > end of the line if they are in Beta 2 of the next version? > > -- > > MichKa > > a new book on internationalization in VB at > > http://www.i18nWithVB.com/ > > > Not trying to start any rumors here ... I thought I'd heard somewhere > that > > > it wouldn't be continued. Michael, if you haven't heard anything, I > must > > be > > > mistaken. My apologies. > > > -- > > > Paul Brower > > > http://www.browerconsulting.com > > > DO NOT EMAIL ME > > wrote > > > > Huh? What are you talking about??? > > > > -- > > > > MichKa > > > > a new book on internationalization in VB at > > > > http://www.i18nWithVB.com/ > > > > > Access 10? I thought Access 2000 was the end of the line. > > > > > -- > > > > > Paul Brower > > > > > http://www.browerconsulting.com > > > > > DO NOT EMAIL ME message > > > > > > I was looking around for some easier way which doesn't exist. The > > > user > > > > > > NEEDS to be able to browse the whole thing, or to get a close > > > imitation > > > > of > > > > > > that. Essentially, if I went the adp route, I wouldn't be > rewriting > > > jet > > > > > > but, along the lines of what you said, creating a form with a > > > datasheet > > > > > that > > > > > > opens pulling the last n records and that has a custom back > > navigation > > > > > > button that pulls the previous n records. Anyway, the whole thing > > > would > > > > > > still be slower and much less useful than just having the whole > > table > > > > > there > > > > > > in the first place. > > > > > > But Michael Kaplan makes a strong case for using linked tables in > > mdb > > > to > > > > > sql > > > > > > server instead of adps. I could avoid this code then, since it's > > only > > > 3 > > > > > or > > > > > > 4 seconds to open the whole table that way (odbc) instead of the > adp > > > way > > > > > > (60+ secs). But I'm still weighing the pro's and con's. I could > > try > > > > > > sticking with jet mdbs on the backend for another year and see how > > > this > > > > > > improves with access 10. > > > > > > > "I know one can probably custom code all of this, but I thought > > > there > > > > > must > > > > > > > be > > > > > > > an easier way to duplicate the behavior of the mdb file " > > > > > > > What makes you think that re-writing the Jet engine is 'easy'? > > > > > > > I suggest using forms and code to jump to small portions of the > > > table. > > > > > > > Do not use the table directly. > > > > > > > -- > > > > > > > Joe > > > > > > > Access MVP > > > > > > > Check out Dev Ashish's web site for answers to common questions > > > > > > > http://www.mvps.org/access/ > message > > > > > > > > Small question, but still a question: What is the best way of > > > > getting > > > > > a > > > > > > > > table in an Access adp file to behave like a linked table in > an > > > mdb > > > > > > file? > > > > > > > > I mean in this respect: > > > > > > > > Table A has 500,000 rows in order from 1 to 500,000 (primary > key > > > > > order). > > > > > > > > In an mdb file (linked to the same backend that the adp is > > using), > > > > the > > > > > > > user > > > > > > > > opens Table A, sees records 1-100 (in order from 1 at the top > to > > > 100 > > > > > at > > > > > > > the > > > > > > > > bottom), presses the move last button, and access immediately > > > jumps > > > > to > > > > > > > > records 499,900 to 500,000 (in order from 499,900 at the top > to > > > > > 500,000 > > > > > > at > > > > > > > > bottom), without loading all the intermediary records before > > > jumping > > > > > > (and > > > > > > > > while still being able to see the records in between if he so > > > > > chooses). > > > > > > > > In an adp file, user opens Table A, sees records 1-100, and > > can't > > > > get > > > > > to > > > > > > > > records 499,900 to 500,000 without actually loading all the > > > > > intermediary > > > > > > > > records (takes a long time). > > > > > > > > I know one can probably custom code all of this, but I thought > > > there > > > > > > must > > > > > > > be > > > > > > > > an easier way to duplicate the behavior of the mdb file in the > > adp > > > > > file. > > > > > > > Or > > > > > > > > what is the easiest way to do this? > > > > > > > > Note all the things that have to duplicated: potential access > to > > > the > > > > > > whole > > > > > > > > table, primary key order from top to bottom, and the quick > jump > > to > > > > the > > > > > > > end, > > > > > > > > i.e. I need a close imitation of the mdb file behavior.
Sat, 19 Apr 2003 23:55:36 GMT

Denis Mcmaho #12 / 13	Make adp table behave like linked mdb table. On Mon, 30 Oct 2000 09:23:42 -0800, "Paul Brower" Quote: >Access 10? I thought Access 2000 was the end of the line. Access 2000 is the poduct name, 9 is the version. Rgds Denis -- Denis McMahon Mobile: +44 7802 468949 I always trim ng when posting!
Fri, 25 Apr 2003 03:00:00 GMT

Page 1 of 1

[ 13 post ]