VBA, Module libraries not found

Module libraries not found

Author	Message
Dennis Glaese #1 / 23	Module libraries not found I have Access 97 both at home and at work. I have a database application, with code, which I copied from home to my work laptop. When I run the application on the laptop I get a "cannot find project or library" message and the de{filter} identifies a string function (LEFT in this case). The Help button has me try to find add-ins which may not be present. Now the strange part. If I create a new blank DB on the laptop and copy all the tables, queries, forms, reports, and modules to the blank DB, IT RUNS FINE!!! I've looked everywhere I can think of to find where or why the home-DB doesn't work on the laptop. Bye the way, the laptop-DB works just fine on the home computer. Any suggestions?
Wed, 03 Dec 2003 03:30:14 GMT

Brendan Reynold #2 / 23	Module libraries not found It's a missing reference. If you're not using any custom controls or automation, the most likely culprit is probably the DAO reference. Access 97 shipped originally with DAO 3.50, while later service releases introduced DAO 3.51. Open any module, or hold down the Ctrl key while pressing G to open the Immediate window, and select References from the Tools menu. Look for any marked 'missing'. If it's the DAO reference, unselect the one marked missing and select the version that is installed on that PC. But you'll have to do it again the next time you move the database from once PC to the other. For a more permanent fix, make sure both PCs are at the same service release level. -- Brendan Reynolds http://www.--.com/ I have Access 97 both at home and at work. I have a database application, with code, which I copied from home to my work laptop. When I run the application on the laptop I get a "cannot find project or library" message and the de{filter*} identifies a string function (LEFT in this case). The Help button has me try to find add-ins which may not be present. Now the strange part. If I create a new blank DB on the laptop and copy all the tables, queries, forms, reports, and modules to the blank DB, IT RUNS FINE!!! I've looked everywhere I can think of to find where or why the home-DB doesn't work on the laptop. Bye the way, the laptop-DB works just fine on the home computer. Any suggestions?
Wed, 03 Dec 2003 03:37:51 GMT

Dennis Glaese #3 / 23	Module libraries not found When this first happened I suspected a version problem, so I re-installed Access on the laptop from the same CD as the home computer, but the problem still exists. And why does creating a new DB solve the problem? The DAO reference is checked on the laptop (I'm not at home). When I look at the References list in both databases (on the laptop), they are not the same! But the DAO reference is 3.5 in both. The home-DB opened on the laptop shows 2 missing references: ProtoView Time Control Lead Control Module(8.0) I'm not using anything from either of those, and neither is referenced by the laptop-DB (those aren't even on the references list) Dennis Glaeser Quote: -----Original Message----- It's a missing reference. If you're not using any custom controls or automation, the most likely culprit is probably the DAO reference. Access 97 shipped originally with DAO 3.50, while later service releases introduced DAO 3.51. Open any module, or hold down the Ctrl key while pressing G to open the Immediate window, and select References from the Tools menu. Look for any marked 'missing'. If it's the DAO reference, unselect the one marked missing and select the version that is installed on that PC. But you'll have to do it again the next time you move the database from once PC to the other. For a more permanent fix, make sure both PCs are at the same service release level. -- Brendan Reynolds http://www.--.com/ I have Access 97 both at home and at work. I have a database application, with code, which I copied from home to my work laptop. When I run the application on the laptop I get a "cannot find project or library" message and the de{filter*} identifies a string function (LEFT in this case). The Help button has me try to find add-ins which may not be present. Now the strange part. If I create a new blank DB on the laptop and copy all the tables, queries, forms, reports, and modules to the blank DB, IT RUNS FINE!!! I've looked everywhere I can think of to find where or why the home-DB doesn't work on the laptop. Bye the way, the laptop-DB works just fine on the home computer. Any suggestions? .
Wed, 03 Dec 2003 04:13:05 GMT

Douglas J. Steel #4 / 23	Module libraries not found Why it matters if you create a new DB is that references are at a database level. Creating a new database starts it with "fresh" references. If you're not using specific references, remove them from the list. If Access can't find one of the references, it affects its ability to use any of the references. For far more than you could ever want to know about this problem, check out http://www.--.com/ homepage. HTH -- Doug Steele, Microsoft Access MVP http://www.--.com/ When this first happened I suspected a version problem, so I re-installed Access on the laptop from the same CD as the home computer, but the problem still exists. And why does creating a new DB solve the problem? The DAO reference is checked on the laptop (I'm not at home). When I look at the References list in both databases (on the laptop), they are not the same! But the DAO reference is 3.5 in both. The home-DB opened on the laptop shows 2 missing references: ProtoView Time Control Lead Control Module(8.0) I'm not using anything from either of those, and neither is referenced by the laptop-DB (those aren't even on the references list) Dennis Glaeser Quote: -----Original Message----- It's a missing reference. If you're not using any custom controls or automation, the most likely culprit is probably the DAO reference. Access 97 shipped originally with DAO 3.50, while later service releases introduced DAO 3.51. Open any module, or hold down the Ctrl key while pressing G to open the Immediate window, and select References from the Tools menu. Look for any marked 'missing'. If it's the DAO reference, unselect the one marked missing and select the version that is installed on that PC. But you'll have to do it again the next time you move the database from once PC to the other. For a more permanent fix, make sure both PCs are at the same service release level. -- Brendan Reynolds http://www.--.com/ I have Access 97 both at home and at work. I have a database application, with code, which I copied from home to my work laptop. When I run the application on the laptop I get a "cannot find project or library" message and the de{filter*} identifies a string function (LEFT in this case). The Help button has me try to find add-ins which may not be present. Now the strange part. If I create a new blank DB on the laptop and copy all the tables, queries, forms, reports, and modules to the blank DB, IT RUNS FINE!!! I've looked everywhere I can think of to find where or why the home-DB doesn't work on the laptop. Bye the way, the laptop-DB works just fine on the home computer. Any suggestions? .
Wed, 03 Dec 2003 07:19:48 GMT

david #5 / 23	Module libraries not found Quote: > http://www.--.com/ Except that you repeat the story about Access first checking for RefLibPaths in the registry. That was in the A97 documentation (hidden - not in the index) and is now in the A2K documentation. Did you ever get it to work with A97? Have you ever tested it with A2000? Note that the A97 documentation specifically referred only to VB projects in mdb, mde, mda. - which is what I tried to do. (Also, note that although A97 could 'find' mde's in the current directory, it could not reliably 'use' them. I am not sure to what extent this depended on the operating system, service pack, or use of mde instead of mdb.) (Also, note that it checks memory before it checks the current directory -- in Win98 if you try and run multiple copies of your application from different directories, A97 will try to use the MDE copy in memory rather than the MDE copy in the local directory if the MDE is not in the referenced path. So how does this work in Win2K? Do separate copies get separate environments, in which case the already loaded MDE's will not be used?) (david) Quote: > Why it matters if you create a new DB is that references are at a database > level. Creating a new database starts it with "fresh" references. > If you're not using specific references, remove them from the list. If > Access can't find one of the references, it affects its ability to use any > of the references. > For far more than you could ever want to know about this problem, check out > http://www.--.com/ > homepage. > HTH > -- > Doug Steele, Microsoft Access MVP > http://www.--.com/ > When this first happened I suspected a version problem, so I re-installed > Access > on the laptop from the same CD as the home computer, but the problem still > exists. > And why does creating a new DB solve the problem? > The DAO reference is checked on the laptop (I'm not at home). > When I look at the References list in both databases (on the laptop), they > are not > the same! But the DAO reference is 3.5 in both. > The home-DB opened on the laptop shows 2 missing references: > ProtoView Time Control > Lead Control Module(8.0) > I'm not using anything from either of those, and neither is referenced by > the > laptop-DB (those aren't even on the references list) > Dennis Glaeser > -----Original Message----- > It's a missing reference. If you're not using any custom controls or > automation, the most likely culprit is probably the DAO reference. Access 97 > shipped originally with DAO 3.50, while later service releases introduced > DAO 3.51. > Open any module, or hold down the Ctrl key while pressing G to open the > Immediate window, and select References from the Tools menu. Look for any > marked 'missing'. If it's the DAO reference, unselect the one marked missing > and select the version that is installed on that PC. But you'll have to do > it again the next time you move the database from once PC to the other. For > a more permanent fix, make sure both PCs are at the same service release > level. > -- > Brendan Reynolds > http://www.--.com/ > I have Access 97 both at home and at work. I have a database application, > with > code, which I copied from home to my work laptop. When I run the > application on > the laptop I get a "cannot find project or library" message and the de{filter} > identifies a string function (LEFT in this case). The Help button has me > try to > find add-ins which may not be present. > Now the strange part. If I create a new blank DB on the laptop and copy all > the > tables, queries, forms, reports, and modules to the blank DB, IT RUNS > FINE!!! > I've looked everywhere I can think of to find where or why the home-DB > doesn't > work on the laptop. Bye the way, the laptop-DB works just fine on the home > computer. > Any suggestions? > .
Thu, 04 Dec 2003 18:45:33 GMT

Douglas J. Steel #6 / 23	Module libraries not found As I explicitly state on the page, most of the information comes from Microsoft. To be perfectly honest, I haven't needed to experiment, as I don't experience this problem. I do not use Access 2000, so obviously I wouldn't have done any testing with it. If you haven't already seen it, you should see what Michka's posted about this topic at http://www.--.com/ -- Doug Steele, Microsoft Access MVP http://www.--.com/ Quote: > > http://www.--.com/ > Except that you repeat the story about Access first checking for RefLibPaths > in the registry. That was in the A97 documentation (hidden - not in the index) > and is now in the A2K documentation. Did you ever get it to work with A97? > Have you ever tested it with A2000? Note that the A97 documentation > specifically referred only to VB projects in mdb, mde, mda. - which is what I > tried to do. > (Also, note that although A97 could 'find' mde's in the current directory, it > could not reliably 'use' them. I am not sure to what extent this depended on > the operating system, service pack, or use of mde instead of mdb.) > (Also, note that it checks memory before it checks the current directory -- > in Win98 if you try and run multiple copies of your application from different > directories, A97 will try to use the MDE copy in memory rather than the MDE > copy in the local directory if the MDE is not in the referenced path. So how > does this work in Win2K? Do separate copies get separate environments, > in which case the already loaded MDE's will not be used?) > (david) - Hide quoted text - - Show quoted text - Quote: > > Why it matters if you create a new DB is that references are at a database > > level. Creating a new database starts it with "fresh" references. > > If you're not using specific references, remove them from the list. If > > Access can't find one of the references, it affects its ability to use any > > of the references. > > For far more than you could ever want to know about this problem, check out > > http://www.--.com/ > > homepage. > > HTH > > -- > > Doug Steele, Microsoft Access MVP > > http://www.--.com/ > > When this first happened I suspected a version problem, so I re-installed > > Access > > on the laptop from the same CD as the home computer, but the problem still > > exists. > > And why does creating a new DB solve the problem? > > The DAO reference is checked on the laptop (I'm not at home). > > When I look at the References list in both databases (on the laptop), they > > are not > > the same! But the DAO reference is 3.5 in both. > > The home-DB opened on the laptop shows 2 missing references: > > ProtoView Time Control > > Lead Control Module(8.0) > > I'm not using anything from either of those, and neither is referenced by > > the > > laptop-DB (those aren't even on the references list) > > Dennis Glaeser > > -----Original Message----- > > It's a missing reference. If you're not using any custom controls or > > automation, the most likely culprit is probably the DAO reference. Access 97 > > shipped originally with DAO 3.50, while later service releases introduced > > DAO 3.51. > > Open any module, or hold down the Ctrl key while pressing G to open the > > Immediate window, and select References from the Tools menu. Look for any > > marked 'missing'. If it's the DAO reference, unselect the one marked missing > > and select the version that is installed on that PC. But you'll have to do > > it again the next time you move the database from once PC to the other. For > > a more permanent fix, make sure both PCs are at the same service release > > level. > > -- > > Brendan Reynolds > > http://www.--.com/ > > I have Access 97 both at home and at work. I have a database application, > > with > > code, which I copied from home to my work laptop. When I run the > > application on > > the laptop I get a "cannot find project or library" message and the de{filter} > > identifies a string function (LEFT in this case). The Help button has me > > try to > > find add-ins which may not be present. > > Now the strange part. If I create a new blank DB on the laptop and copy all > > the > > tables, queries, forms, reports, and modules to the blank DB, IT RUNS > > FINE!!! > > I've looked everywhere I can think of to find where or why the home-DB > > doesn't > > work on the laptop. Bye the way, the laptop-DB works just fine on the home > > computer. > > Any suggestions? > > .
Thu, 04 Dec 2003 21:20:35 GMT

david #7 / 23	Module libraries not found Ok, that was ruder than I intended it to be. In fact, I didn't intend to be rude at all. God knows I make enough mistakes of my own, but I think that bit of information is wrong. (david) Quote: > As I explicitly state on the page, most of the information comes from > Microsoft. To be perfectly honest, I haven't needed to experiment, as I > don't experience this problem. I do not use Access 2000, so obviously I > wouldn't have done any testing with it. > If you haven't already seen it, you should see what Michka's posted about > this topic at http://www.--.com/ > -- > Doug Steele, Microsoft Access MVP > http://www.--.com/ > > > http://www.--.com/ > > Except that you repeat the story about Access first checking for > RefLibPaths > > in the registry. That was in the A97 documentation (hidden - not in the > index) > > and is now in the A2K documentation. Did you ever get it to work with > A97? > > Have you ever tested it with A2000? Note that the A97 documentation > > specifically referred only to VB projects in mdb, mde, mda. - which is > what I > > tried to do. > > (Also, note that although A97 could 'find' mde's in the current directory, > it > > could not reliably 'use' them. I am not sure to what extent this depended > on > > the operating system, service pack, or use of mde instead of mdb.) > > (Also, note that it checks memory before it checks the current > directory -- > > in Win98 if you try and run multiple copies of your application from > different > > directories, A97 will try to use the MDE copy in memory rather than the > MDE > > copy in the local directory if the MDE is not in the referenced path. So > how > > does this work in Win2K? Do separate copies get separate environments, > > in which case the already loaded MDE's will not be used?) > > (david) > > > Why it matters if you create a new DB is that references are at a > database > > > level. Creating a new database starts it with "fresh" references. > > > If you're not using specific references, remove them from the list. If > > > Access can't find one of the references, it affects its ability to use > any > > > of the references. > > > For far more than you could ever want to know about this problem, check > out > > > http://www.--.com/ > > > homepage. > > > HTH > > > -- > > > Doug Steele, Microsoft Access MVP > > > http://www.--.com/ > > > When this first happened I suspected a version problem, so I > re-installed > > > Access > > > on the laptop from the same CD as the home computer, but the problem > still > > > exists. > > > And why does creating a new DB solve the problem? > > > The DAO reference is checked on the laptop (I'm not at home). > > > When I look at the References list in both databases (on the laptop), > they > > > are not > > > the same! But the DAO reference is 3.5 in both. > > > The home-DB opened on the laptop shows 2 missing references: > > > ProtoView Time Control > > > Lead Control Module(8.0) > > > I'm not using anything from either of those, and neither is referenced > by > > > the > > > laptop-DB (those aren't even on the references list) > > > Dennis Glaeser > > > -----Original Message----- > > > It's a missing reference. If you're not using any custom controls or > > > automation, the most likely culprit is probably the DAO reference. > Access 97 > > > shipped originally with DAO 3.50, while later service releases > introduced > > > DAO 3.51. > > > Open any module, or hold down the Ctrl key while pressing G to open the > > > Immediate window, and select References from the Tools menu. Look for > any > > > marked 'missing'. If it's the DAO reference, unselect the one marked > missing > > > and select the version that is installed on that PC. But you'll have to > do > > > it again the next time you move the database from once PC to the other. > For > > > a more permanent fix, make sure both PCs are at the same service release > > > level. > > > -- > > > Brendan Reynolds > > > http://www.--.com/ > > > I have Access 97 both at home and at work. I have a database > application, > > > with > > > code, which I copied from home to my work laptop. When I run the > > > application on > > > the laptop I get a "cannot find project or library" message and the > de{filter} > > > identifies a string function (LEFT in this case). The Help button has > me > > > try to > > > find add-ins which may not be present. > > > Now the strange part. If I create a new blank DB on the laptop and copy > all > > > the > > > tables, queries, forms, reports, and modules to the blank DB, IT RUNS > > > FINE!!! > > > I've looked everywhere I can think of to find where or why the home-DB > > > doesn't > > > work on the laptop. Bye the way, the laptop-DB works just fine on the > home > > > computer. > > > Any suggestions? > > > .
Fri, 05 Dec 2003 11:48:33 GMT

Dennis Glaese #8 / 23	Module libraries not found Thanks, simply unchecking the "Missing References" seems to solve the problem. I don't know why I didn't just try that earlier (probably figured Access knew what it needs and what it doesn't). This newsgroup is a wealth of info for us 'shadetree mechanics' !!! Dennis Glaeser Quote: -----Original Message----- Why it matters if you create a new DB is that references are at a database level. Creating a new database starts it with "fresh" references. If you're not using specific references, remove them from the list. If Access can't find one of the references, it affects its ability to use any of the references. For far more than you could ever want to know about this problem, check out http://www.--.com/ homepage. HTH -- Doug Steele, Microsoft Access MVP http://www.--.com/ When this first happened I suspected a version problem, so I re-installed Access on the laptop from the same CD as the home computer, but the problem still exists. And why does creating a new DB solve the problem? The DAO reference is checked on the laptop (I'm not at home). When I look at the References list in both databases (on the laptop), they are not the same! But the DAO reference is 3.5 in both. The home-DB opened on the laptop shows 2 missing references: ProtoView Time Control Lead Control Module(8.0) I'm not using anything from either of those, and neither is referenced by the laptop-DB (those aren't even on the references list) Dennis Glaeser -----Original Message----- It's a missing reference. If you're not using any custom controls or automation, the most likely culprit is probably the DAO reference. Access 97 shipped originally with DAO 3.50, while later service releases introduced DAO 3.51. Open any module, or hold down the Ctrl key while pressing G to open the Immediate window, and select References from the Tools menu. Look for any marked 'missing'. If it's the DAO reference, unselect the one marked missing and select the version that is installed on that PC. But you'll have to do it again the next time you move the database from once PC to the other. For a more permanent fix, make sure both PCs are at the same service release level. -- Brendan Reynolds http://www.--.com/ I have Access 97 both at home and at work. I have a database application, with code, which I copied from home to my work laptop. When I run the application on the laptop I get a "cannot find project or library" message and the de{filter*} identifies a string function (LEFT in this case). The Help button has me try to find add-ins which may not be present. Now the strange part. If I create a new blank DB on the laptop and copy all the tables, queries, forms, reports, and modules to the blank DB, IT RUNS FINE!!! I've looked everywhere I can think of to find where or why the home-DB doesn't work on the laptop. Bye the way, the laptop-DB works just fine on the home computer. Any suggestions? .. .
Sat, 06 Dec 2003 21:20:51 GMT

Douglas J. Steel #9 / 23	Module libraries not found As I promised (in a private e-mail), I've bounced this off Microsoft and the other MVPs. The reply I got back (from two different sources) was that when checking for references, memory is always checked first (as stated in the article), and that Access 97 and Access 2000 are consistent in the this regard. HTH -- Doug Steele, Microsoft Access MVP http://www.--.com/ Quote: > Ok, that was ruder than I intended it to be. In fact, I didn't intend to > be rude at all. God knows I make enough mistakes of my own, but > I think that bit of information is wrong. > (david) Quote: > > As I explicitly state on the page, most of the information comes from > > Microsoft. To be perfectly honest, I haven't needed to experiment, as I > > don't experience this problem. I do not use Access 2000, so obviously I > > wouldn't have done any testing with it. > > If you haven't already seen it, you should see what Michka's posted about > > this topic at http://www.--.com/ > > -- > > Doug Steele, Microsoft Access MVP > > http://www.--.com/ > > > > http://www.--.com/ > > > Except that you repeat the story about Access first checking for > > RefLibPaths > > > in the registry. That was in the A97 documentation (hidden - not in the > > index) > > > and is now in the A2K documentation. Did you ever get it to work with > > A97? > > > Have you ever tested it with A2000? Note that the A97 documentation > > > specifically referred only to VB projects in mdb, mde, mda. - which is > > what I > > > tried to do. > > > (Also, note that although A97 could 'find' mde's in the current directory, > > it > > > could not reliably 'use' them. I am not sure to what extent this depended > > on > > > the operating system, service pack, or use of mde instead of mdb.) > > > (Also, note that it checks memory before it checks the current > > directory -- > > > in Win98 if you try and run multiple copies of your application from > > different > > > directories, A97 will try to use the MDE copy in memory rather than the > > MDE > > > copy in the local directory if the MDE is not in the referenced path. So > > how > > > does this work in Win2K? Do separate copies get separate environments, > > > in which case the already loaded MDE's will not be used?) > > > (david) > > > > Why it matters if you create a new DB is that references are at a > > database > > > > level. Creating a new database starts it with "fresh" references. > > > > If you're not using specific references, remove them from the list. If > > > > Access can't find one of the references, it affects its ability to use > > any > > > > of the references. > > > > For far more than you could ever want to know about this problem, check > > out > > > > http://www.--.com/ > > > > homepage. > > > > HTH > > > > -- > > > > Doug Steele, Microsoft Access MVP > > > > http://www.--.com/ > > > > When this first happened I suspected a version problem, so I > > re-installed > > > > Access > > > > on the laptop from the same CD as the home computer, but the problem > > still > > > > exists. > > > > And why does creating a new DB solve the problem? > > > > The DAO reference is checked on the laptop (I'm not at home). > > > > When I look at the References list in both databases (on the laptop), > > they > > > > are not > > > > the same! But the DAO reference is 3.5 in both. > > > > The home-DB opened on the laptop shows 2 missing references: > > > > ProtoView Time Control > > > > Lead Control Module(8.0) > > > > I'm not using anything from either of those, and neither is referenced > > by > > > > the > > > > laptop-DB (those aren't even on the references list) > > > > Dennis Glaeser > > > > -----Original Message----- > > > > It's a missing reference. If you're not using any custom controls or > > > > automation, the most likely culprit is probably the DAO reference. > > Access 97 > > > > shipped originally with DAO 3.50, while later service releases > > introduced > > > > DAO 3.51. > > > > Open any module, or hold down the Ctrl key while pressing G to open the > > > > Immediate window, and select References from the Tools menu. Look for > > any > > > > marked 'missing'. If it's the DAO reference, unselect the one marked > > missing > > > > and select the version that is installed on that PC. But you'll have to > > do > > > > it again the next time you move the database from once PC to the other. > > For > > > > a more permanent fix, make sure both PCs are at the same service release > > > > level. > > > > -- > > > > Brendan Reynolds > > > > http://www.--.com/ > > > > I have Access 97 both at home and at work. I have a database > > application, > > > > with > > > > code, which I copied from home to my work laptop. When I run the > > > > application on > > > > the laptop I get a "cannot find project or library" message and the > > de{filter*} > > > > identifies a string function (LEFT in this case). The Help button has > > me > > > > try to > > > > find add-ins which may not be present. > > > > Now the strange part. If I create a new blank DB on the laptop and copy > > all > > > > the > > > > tables, queries, forms, reports, and modules to the blank DB, IT RUNS > > > > FINE!!! > > > > I've looked everywhere I can think of to find where or why the home-DB > > > > doesn't > > > > work on the laptop. Bye the way, the laptop-DB works just fine on the > > home > > > > computer. > > > > Any suggestions? > > > > .
Sun, 07 Dec 2003 04:50:16 GMT

Stephen K. Youn #10 / 23	Module libraries not found The RefLibPaths registry entry does work in Access 97. In my case, I distribute a front-end compiled .Mde, with a reference to a compiled library .Mde, using the ODE installer. At install time, the users install to any drive or directory of their choice, but I make sure there is a RefLibPaths entry in the registry for my library compiled .Mde, using the ODE setup. The front-end compiled .Mde does successfully find the library when the user runs the application. - Steve Quote: > > http://www.--.com/ at my > Except that you repeat the story about Access first checking for RefLibPaths > in the registry. That was in the A97 documentation (hidden - not in the index) > and is now in the A2K documentation. Did you ever get it to work with A97? > Have you ever tested it with A2000? Note that the A97 documentation > specifically referred only to VB projects in mdb, mde, mda. - which is what I > tried to do. > (Also, note that although A97 could 'find' mde's in the current directory, it > could not reliably 'use' them. I am not sure to what extent this depended on > the operating system, service pack, or use of mde instead of mdb.) > (Also, note that it checks memory before it checks the current directory -- > in Win98 if you try and run multiple copies of your application from different > directories, A97 will try to use the MDE copy in memory rather than the MDE > copy in the local directory if the MDE is not in the referenced path. So how > does this work in Win2K? Do separate copies get separate environments, > in which case the already loaded MDE's will not be used?) > (david) - Hide quoted text - - Show quoted text - Quote: > > Why it matters if you create a new DB is that references are at a database > > level. Creating a new database starts it with "fresh" references. > > If you're not using specific references, remove them from the list. If > > Access can't find one of the references, it affects its ability to use any > > of the references. > > For far more than you could ever want to know about this problem, check out > > http://www.--.com/ at my > > homepage. > > HTH > > -- > > Doug Steele, Microsoft Access MVP > > http://www.--.com/ > > When this first happened I suspected a version problem, so I re-installed > > Access > > on the laptop from the same CD as the home computer, but the problem still > > exists. > > And why does creating a new DB solve the problem? > > The DAO reference is checked on the laptop (I'm not at home). > > When I look at the References list in both databases (on the laptop), they > > are not > > the same! But the DAO reference is 3.5 in both. > > The home-DB opened on the laptop shows 2 missing references: > > ProtoView Time Control > > Lead Control Module(8.0) > > I'm not using anything from either of those, and neither is referenced by > > the > > laptop-DB (those aren't even on the references list) > > Dennis Glaeser > > -----Original Message----- > > It's a missing reference. If you're not using any custom controls or > > automation, the most likely culprit is probably the DAO reference. Access 97 - Hide quoted text - - Show quoted text - Quote: > > shipped originally with DAO 3.50, while later service releases introduced > > DAO 3.51. > > Open any module, or hold down the Ctrl key while pressing G to open the > > Immediate window, and select References from the Tools menu. Look for any > > marked 'missing'. If it's the DAO reference, unselect the one marked missing > > and select the version that is installed on that PC. But you'll have to do > > it again the next time you move the database from once PC to the other. For > > a more permanent fix, make sure both PCs are at the same service release > > level. > > -- > > Brendan Reynolds > > http://www.--.com/ > > I have Access 97 both at home and at work. I have a database application, > > with > > code, which I copied from home to my work laptop. When I run the > > application on > > the laptop I get a "cannot find project or library" message and the de{filter} > > identifies a string function (LEFT in this case). The Help button has me > > try to > > find add-ins which may not be present. > > Now the strange part. If I create a new blank DB on the laptop and copy all > > the > > tables, queries, forms, reports, and modules to the blank DB, IT RUNS > > FINE!!! > > I've looked everywhere I can think of to find where or why the home-DB > > doesn't > > work on the laptop. Bye the way, the laptop-DB works just fine on the home > > computer. > > Any suggestions? > > .
Sun, 07 Dec 2003 05:05:55 GMT

david #11 / 23	Module libraries not found I've been off line for a week. I've been testing on WinME, using A97 SR2 This is my registry setting: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPaths] "DB1.mdb"="C:\\DB1.MDB" "db1"="c:\\db1.mdb" "c:\\capix\\db1.mdb"="c:\\db1.mdb" db1 is the project name, DB1.mdb is the file name c:\\capix\\db1.mdb is the fullpath to the original MDE. (Out of desperation I tried all three, because the first didn't work) c:\\db1.mdb is the new location of project db1 --------- do you notice anything wrong? what operating system(s) have you tested with? --------- (david) Quote: > The RefLibPaths registry entry does work in Access 97. > In my case, I distribute a front-end compiled .Mde, with a > reference to a compiled library .Mde, using the ODE installer. At > install time, the users install to any drive or directory of > their choice, but I make sure there is a RefLibPaths entry in the > registry for my library compiled .Mde, using the ODE setup. The > front-end compiled .Mde does successfully find the library when > the user runs the application. > - Steve > > > http://www.--.com/ > at my > > Except that you repeat the story about Access first checking > for RefLibPaths > > in the registry. That was in the A97 documentation (hidden - > not in the index) > > and is now in the A2K documentation. Did you ever get it to > work with A97? > > Have you ever tested it with A2000? Note that the A97 > documentation > > specifically referred only to VB projects in mdb, mde, mda. - > which is what I > > tried to do. > > (Also, note that although A97 could 'find' mde's in the current > directory, it > > could not reliably 'use' them. I am not sure to what extent > this depended on > > the operating system, service pack, or use of mde instead of > mdb.) > > (Also, note that it checks memory before it checks the current > directory -- > > in Win98 if you try and run multiple copies of your application > from different > > directories, A97 will try to use the MDE copy in memory rather > than the MDE > > copy in the local directory if the MDE is not in the referenced > path. So how > > does this work in Win2K? Do separate copies get separate > environments, > > in which case the already loaded MDE's will not be used?) > > (david) > > > Why it matters if you create a new DB is that references are > at a database > > > level. Creating a new database starts it with "fresh" > references. > > > If you're not using specific references, remove them from the > list. If > > > Access can't find one of the references, it affects its > ability to use any > > > of the references. > > > For far more than you could ever want to know about this > problem, check out > > > http://www.--.com/ > at my > > > homepage. > > > HTH > > > -- > > > Doug Steele, Microsoft Access MVP > > > http://www.--.com/ > > > When this first happened I suspected a version problem, so I > re-installed > > > Access > > > on the laptop from the same CD as the home computer, but the > problem still > > > exists. > > > And why does creating a new DB solve the problem? > > > The DAO reference is checked on the laptop (I'm not at home). > > > When I look at the References list in both databases (on the > laptop), they > > > are not > > > the same! But the DAO reference is 3.5 in both. > > > The home-DB opened on the laptop shows 2 missing references: > > > ProtoView Time Control > > > Lead Control Module(8.0) > > > I'm not using anything from either of those, and neither is > referenced by > > > the > > > laptop-DB (those aren't even on the references list) > > > Dennis Glaeser > > > -----Original Message----- > > > It's a missing reference. If you're not using any custom > controls or > > > automation, the most likely culprit is probably the DAO > reference. Access 97 > > > shipped originally with DAO 3.50, while later service > releases introduced > > > DAO 3.51. > > > Open any module, or hold down the Ctrl key while pressing G > to open the > > > Immediate window, and select References from the Tools menu. > Look for any > > > marked 'missing'. If it's the DAO reference, unselect the one > marked missing > > > and select the version that is installed on that PC. But > you'll have to do > > > it again the next time you move the database from once PC to > the other. For > > > a more permanent fix, make sure both PCs are at the same > service release > > > level. > > > -- > > > Brendan Reynolds > > > http://www.--.com/ > > > I have Access 97 both at home and at work. I have a database > application, > > > with > > > code, which I copied from home to my work laptop. When I run > the > > > application on > > > the laptop I get a "cannot find project or library" message > and the de{filter} > > > identifies a string function (LEFT in this case). The Help > button has me > > > try to > > > find add-ins which may not be present. > > > Now the strange part. If I create a new blank DB on the > laptop and copy all > > > the > > > tables, queries, forms, reports, and modules to the blank DB, > IT RUNS > > > FINE!!! > > > I've looked everywhere I can think of to find where or why > the home-DB > > > doesn't > > > work on the laptop. Bye the way, the laptop-DB works just > fine on the home > > > computer. > > > Any suggestions? > > > .
Sun, 14 Dec 2003 08:31:08 GMT

david #12 / 23	Module libraries not found hang on, are you installing the base MDE in the same directory as the referenced MDE? In that case RefLibPaths is not always tested -- the search path for referenced projects includes the current folder. (david) Quote: > I've been off line for a week. > I've been testing on WinME, using A97 SR2 > This is my registry setting: > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPaths] > "DB1.mdb"="C:\\DB1.MDB" > "db1"="c:\\db1.mdb" > "c:\\capix\\db1.mdb"="c:\\db1.mdb" > db1 is the project name, > DB1.mdb is the file name > c:\\capix\\db1.mdb is the fullpath to the original MDB. > (Out of desperation I tried all three, because the first didn't work) > c:\\db1.mdb is the new location of project db1 > --------- > do you notice anything wrong? > what operating system(s) have you tested with? > --------- > (david) > > The RefLibPaths registry entry does work in Access 97. > > In my case, I distribute a front-end compiled .Mde, with a > > reference to a compiled library .Mde, using the ODE installer. At > > install time, the users install to any drive or directory of > > their choice, but I make sure there is a RefLibPaths entry in the > > registry for my library compiled .Mde, using the ODE setup. The > > front-end compiled .Mde does successfully find the library when > > the user runs the application. > > - Steve > > > > http://www.--.com/ > > at my > > > Except that you repeat the story about Access first checking > > for RefLibPaths > > > in the registry. That was in the A97 documentation (hidden - > > not in the index) > > > and is now in the A2K documentation. Did you ever get it to > > work with A97? > > > Have you ever tested it with A2000? Note that the A97 > > documentation > > > specifically referred only to VB projects in mdb, mde, mda. - > > which is what I > > > tried to do. > > > (Also, note that although A97 could 'find' mde's in the current > > directory, it > > > could not reliably 'use' them. I am not sure to what extent > > this depended on > > > the operating system, service pack, or use of mde instead of > > mdb.) > > > (Also, note that it checks memory before it checks the current > > directory -- > > > in Win98 if you try and run multiple copies of your application > > from different > > > directories, A97 will try to use the MDE copy in memory rather > > than the MDE > > > copy in the local directory if the MDE is not in the referenced > > path. So how > > > does this work in Win2K? Do separate copies get separate > > environments, > > > in which case the already loaded MDE's will not be used?) > > > (david) > > > > Why it matters if you create a new DB is that references are > > at a database > > > > level. Creating a new database starts it with "fresh" > > references. > > > > If you're not using specific references, remove them from the > > list. If > > > > Access can't find one of the references, it affects its > > ability to use any > > > > of the references. > > > > For far more than you could ever want to know about this > > problem, check out > > > > http://www.--.com/ > > at my > > > > homepage. > > > > HTH > > > > -- > > > > Doug Steele, Microsoft Access MVP > > > > http://www.--.com/ > > > > When this first happened I suspected a version problem, so I > > re-installed > > > > Access > > > > on the laptop from the same CD as the home computer, but the > > problem still > > > > exists. > > > > And why does creating a new DB solve the problem? > > > > The DAO reference is checked on the laptop (I'm not at home). > > > > When I look at the References list in both databases (on the > > laptop), they > > > > are not > > > > the same! But the DAO reference is 3.5 in both. > > > > The home-DB opened on the laptop shows 2 missing references: > > > > ProtoView Time Control > > > > Lead Control Module(8.0) > > > > I'm not using anything from either of those, and neither is > > referenced by > > > > the > > > > laptop-DB (those aren't even on the references list) > > > > Dennis Glaeser > > > > -----Original Message----- > > > > It's a missing reference. If you're not using any custom > > controls or > > > > automation, the most likely culprit is probably the DAO > > reference. Access 97 > > > > shipped originally with DAO 3.50, while later service > > releases introduced > > > > DAO 3.51. > > > > Open any module, or hold down the Ctrl key while pressing G > > to open the > > > > Immediate window, and select References from the Tools menu. > > Look for any > > > > marked 'missing'. If it's the DAO reference, unselect the one > > marked missing > > > > and select the version that is installed on that PC. But > > you'll have to do > > > > it again the next time you move the database from once PC to > > the other. For > > > > a more permanent fix, make sure both PCs are at the same > > service release > > > > level. > > > > -- > > > > Brendan Reynolds > > > > http://www.--.com/ > > > > I have Access 97 both at home and at work. I have a database > > application, > > > > with > > > > code, which I copied from home to my work laptop. When I run > > the > > > > application on > > > > the laptop I get a "cannot find project or library" message > > and the de{filter} > > > > identifies a string function (LEFT in this case). The Help > > button has me > > > > try to > > > > find add-ins which may not be present. > > > > Now the strange part. If I create a new blank DB on the > > laptop and copy all > > > > the > > > > tables, queries, forms, reports, and modules to the blank DB, > > IT RUNS > > > > FINE!!! > > > > I've looked everywhere I can think of to find where or why > > the home-DB > > > > doesn't > > > > work on the laptop. Bye the way, the laptop-DB works just > > fine on the home > > > > computer. > > > > Any suggestions? > > > > .
Sun, 14 Dec 2003 08:59:31 GMT

Stephen K. Youn #13 / 23	Module libraries not found Your first entry looks correct, except for the double backslash. The key NAME is the basic file name including the extension but no path. Its string VALUE is the full path. So in your notation, I would suggest something like: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPa ths] "Db1.mdb"="C:\Db1.mdb" - Steve Quote: > I've been off line for a week. > I've been testing on WinME, using A97 SR2 > This is my registry setting: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPa ths] Quote: > "DB1.mdb"="C:\\DB1.MDB" > "db1"="c:\\db1.mdb" > "c:\\capix\\db1.mdb"="c:\\db1.mdb" > db1 is the project name, > DB1.mdb is the file name > c:\\capix\\db1.mdb is the fullpath to the original MDE. > (Out of desperation I tried all three, because the first didn't work) > c:\\db1.mdb is the new location of project db1 > --------- > do you notice anything wrong? > what operating system(s) have you tested with? > --------- > (david) - Hide quoted text - - Show quoted text - Quote: > > The RefLibPaths registry entry does work in Access 97. > > In my case, I distribute a front-end compiled .Mde, with a > > reference to a compiled library .Mde, using the ODE installer. At > > install time, the users install to any drive or directory of > > their choice, but I make sure there is a RefLibPaths entry in the > > registry for my library compiled .Mde, using the ODE setup. The > > front-end compiled .Mde does successfully find the library when > > the user runs the application. > > - Steve in http://www.--.com/ - Hide quoted text - - Show quoted text - Quote: > > at my > > > Except that you repeat the story about Access first checking > > for RefLibPaths > > > in the registry. That was in the A97 documentation (hidden - > > not in the index) > > > and is now in the A2K documentation. Did you ever get it to > > work with A97? > > > Have you ever tested it with A2000? Note that the A97 > > documentation > > > specifically referred only to VB projects in mdb, mde, mda. - > > which is what I > > > tried to do. > > > (Also, note that although A97 could 'find' mde's in the current > > directory, it > > > could not reliably 'use' them. I am not sure to what extent > > this depended on > > > the operating system, service pack, or use of mde instead of > > mdb.) > > > (Also, note that it checks memory before it checks the current > > directory -- > > > in Win98 if you try and run multiple copies of your application > > from different > > > directories, A97 will try to use the MDE copy in memory rather > > than the MDE > > > copy in the local directory if the MDE is not in the referenced > > path. So how > > > does this work in Win2K? Do separate copies get separate > > environments, > > > in which case the already loaded MDE's will not be used?) > > > (david) > > > > Why it matters if you create a new DB is that references are > > at a database > > > > level. Creating a new database starts it with "fresh" > > references. > > > > If you're not using specific references, remove them from the > > list. If > > > > Access can't find one of the references, it affects its > > ability to use any > > > > of the references. > > > > For far more than you could ever want to know about this > > problem, check out http://www.--.com/ - Hide quoted text - - Show quoted text - Quote: > > at my > > > > homepage. > > > > HTH > > > > -- > > > > Doug Steele, Microsoft Access MVP > > > > http://www.--.com/ > > > > When this first happened I suspected a version problem, so I > > re-installed > > > > Access > > > > on the laptop from the same CD as the home computer, but the > > problem still > > > > exists. > > > > And why does creating a new DB solve the problem? > > > > The DAO reference is checked on the laptop (I'm not at home). > > > > When I look at the References list in both databases (on the > > laptop), they > > > > are not > > > > the same! But the DAO reference is 3.5 in both. > > > > The home-DB opened on the laptop shows 2 missing references: > > > > ProtoView Time Control > > > > Lead Control Module(8.0) > > > > I'm not using anything from either of those, and neither is > > referenced by > > > > the > > > > laptop-DB (those aren't even on the references list) > > > > Dennis Glaeser > > > > -----Original Message----- > > > > It's a missing reference. If you're not using any custom > > controls or > > > > automation, the most likely culprit is probably the DAO > > reference. Access 97 > > > > shipped originally with DAO 3.50, while later service > > releases introduced > > > > DAO 3.51. > > > > Open any module, or hold down the Ctrl key while pressing G > > to open the > > > > Immediate window, and select References from the Tools menu. > > Look for any > > > > marked 'missing'. If it's the DAO reference, unselect the one > > marked missing > > > > and select the version that is installed on that PC. But > > you'll have to do > > > > it again the next time you move the database from once PC to > > the other. For > > > > a more permanent fix, make sure both PCs are at the same > > service release > > > > level. > > > > -- > > > > Brendan Reynolds > > > > http://www.--.com/ > > > > I have Access 97 both at home and at work. I have a database > > application, > > > > with > > > > code, which I copied from home to my work laptop. When I run > > the > > > > application on > > > > the laptop I get a "cannot find project or library" message > > and the de{filter} > > > > identifies a string function (LEFT in this case). The Help > > button has me > > > > try to > > > > find add-ins which may not be present. > > > > Now the strange part. If I create a new blank DB on the > > laptop and copy all > > > > the > > > > tables, queries, forms, reports, and modules to the blank DB, > > IT RUNS > > > > FINE!!! > > > > I've looked everywhere I can think of to find where or why > > the home-DB > > > > doesn't > > > > work on the laptop. Bye the way, the laptop-DB works just > > fine on the home > > > > computer. > > > > Any suggestions? > > > > .
Mon, 15 Dec 2003 03:59:15 GMT

Stephen K. Youn #14 / 23	Module libraries not found My referenced compiled library .Mde file is in a separate subdirectory, NOT in the same directory as the front end compiled .Mde file. So RefLibPaths seems to work for me. I have tested it with Windows 95, 98, NT, and 2000 (not ME), and users can install to different drive letters and paths. It took a while to get it just right, but my RefLibPaths is something like "X.Mde" = "D:\AppRoot\AppSubdir\X.Mde". - Steve Quote: > hang on, are you installing the base MDE in the same directory as the > referenced MDE? In that case RefLibPaths is not always tested -- > the search path for referenced projects includes the current folder. > (david) Quote: > Your first entry looks correct, except for the double backslash. > The key NAME is the basic file name including the extension but > no path. Its string VALUE is the full path. So in your notation, > I would suggest something like: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPa Quote: > ths] > "Db1.mdb"="C:\Db1.mdb" > - Steve in > > I've been off line for a week. > > I've been testing on WinME, using A97 SR2 > > This is my registry setting: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPa - Hide quoted text - - Show quoted text - Quote: > ths] > > "DB1.mdb"="C:\\DB1.MDB" > > "db1"="c:\\db1.mdb" > > "c:\\capix\\db1.mdb"="c:\\db1.mdb" > > db1 is the project name, > > DB1.mdb is the file name > > c:\\capix\\db1.mdb is the fullpath to the original MDE. > > (Out of desperation I tried all three, because the first didn't > work) > > c:\\db1.mdb is the new location of project db1 > > --------- > > do you notice anything wrong? > > what operating system(s) have you tested with? > > --------- > > (david) > > > The RefLibPaths registry entry does work in Access 97. > > > In my case, I distribute a front-end compiled .Mde, with a > > > reference to a compiled library .Mde, using the ODE > installer. At > > > install time, the users install to any drive or directory of > > > their choice, but I make sure there is a RefLibPaths entry in > the > > > registry for my library compiled .Mde, using the ODE setup. > The > > > front-end compiled .Mde does successfully find the library > when > > > the user runs the application. > > > - Steve wrote > in > http://www.--.com/ > > > at my > > > > Except that you repeat the story about Access first > checking > > > for RefLibPaths > > > > in the registry. That was in the A97 documentation > (hidden - > > > not in the index) > > > > and is now in the A2K documentation. Did you ever get it > to > > > work with A97? > > > > Have you ever tested it with A2000? Note that the A97 > > > documentation > > > > specifically referred only to VB projects in mdb, mde, > mda. - > > > which is what I > > > > tried to do. > > > > (Also, note that although A97 could 'find' mde's in the > current > > > directory, it > > > > could not reliably 'use' them. I am not sure to what > extent > > > this depended on > > > > the operating system, service pack, or use of mde instead > of > > > mdb.) > > > > (Also, note that it checks memory before it checks the > current > > > directory -- > > > > in Win98 if you try and run multiple copies of your > application > > > from different > > > > directories, A97 will try to use the MDE copy in memory > rather > > > than the MDE > > > > copy in the local directory if the MDE is not in the > referenced > > > path. So how > > > > does this work in Win2K? Do separate copies get separate > > > environments, > > > > in which case the already loaded MDE's will not be used?) > > > > (david) message > > > > > Why it matters if you create a new DB is that references > are > > > at a database > > > > > level. Creating a new database starts it with "fresh" > > > references. > > > > > If you're not using specific references, remove them from > the > > > list. If > > > > > Access can't find one of the references, it affects its > > > ability to use any > > > > > of the references. > > > > > For far more than you could ever want to know about this > > > problem, check out > http://www.--.com/ > > > at my > > > > > homepage. > > > > > HTH > > > > > -- > > > > > Doug Steele, Microsoft Access MVP > > > > > http://www.--.com/ > > > > > When this first happened I suspected a version problem, > so I > > > re-installed > > > > > Access > > > > > on the laptop from the same CD as the home computer, but > the > > > problem still > > > > > exists. > > > > > And why does creating a new DB solve the problem? > > > > > The DAO reference is checked on the laptop (I'm not at > home). > > > > > When I look at the References list in both databases (on > the > > > laptop), they > > > > > are not > > > > > the same! But the DAO reference is 3.5 in both. > > > > > The home-DB opened on the laptop shows 2 missing > references: > > > > > ProtoView Time Control > > > > > Lead Control Module(8.0) > > > > > I'm not using anything from either of those, and neither > is > > > referenced by > > > > > the > > > > > laptop-DB (those aren't even on the references list) > > > > > Dennis Glaeser > > > > > -----Original Message----- > > > > > It's a missing reference. If you're not using any custom > > > controls or > > > > > automation, the most likely culprit is probably the DAO > > > reference. Access 97 > > > > > shipped originally with DAO 3.50, while later service > > > releases introduced > > > > > DAO 3.51. > > > > > Open any module, or hold down the Ctrl key while pressing > G > > > to open the > > > > > Immediate window, and select References from the Tools > menu. > > > Look for any > > > > > marked 'missing'. If it's the DAO reference, unselect the > one > > > marked missing > > > > > and select the version that is installed on that PC. But > > > you'll have to do > > > > > it again the next time you move the database from once PC > to > > > the other. For > > > > > a more permanent fix, make sure both PCs are at the same > > > service release > > > > > level. > > > > > -- > > > > > Brendan Reynolds > > > > > http://www.--.com/ > > > > > I have Access 97 both at home and at work. I have a > database > > > application, > > > > > with > > > > > code, which I copied from home to my work laptop. When I > run > > > the > > > > > application on > > > > > the laptop I get a "cannot find project or library" > message > > > and the de{filter} > > > > > identifies a string function (LEFT in this case). The > Help > > > button has me > > > > > try to > > > > > find add-ins which may not be present. > > > > > Now the strange part. If I create a new blank DB on the > > > laptop and copy all > > > > > the > > > > > tables, queries, forms, reports, and modules to the blank > DB, > > > IT RUNS > > > > > FINE!!! > > > > > I've looked everywhere I can think of to find where or > why > > > the home-DB > > > > > doesn't > > > > > work on the laptop. Bye the way, the laptop-DB works > just > > > fine on the home > > > > > computer. > > > > > Any suggestions? > > > > > .
Mon, 15 Dec 2003 04:06:37 GMT

david #15 / 23	Module libraries not found I've just tried it again, this time with .MDE instead of .MDB Still no joy. (WinME) Next I will try it on Win2K. I am using an empty A97 database with 1 module containing Sub db1A() End Sub Sub db1B() End Sub as the library project. I am testing from an empty A97 database with 1 module containing Sub db2A() End Sub. I test from the immediate window: call db2A I have added the immediate window button to my toolbar so that I can open the window without having a module open. ----- the \\ in the registry strings are the way the export/import works for .reg files. ----- Quote: > My referenced compiled library .Mde file is in a separate > subdirectory, NOT in the same directory as the front end compiled > .Mde file. So RefLibPaths seems to work for me. > I have tested it with Windows 95, 98, NT, and 2000 (not ME), and > users can install to different drive letters and paths. It took a > while to get it just right, but my RefLibPaths is something like > "X.Mde" = "D:\AppRoot\AppSubdir\X.Mde". > - Steve > > hang on, are you installing the base MDE in the same directory > as the > > referenced MDE? In that case RefLibPaths is not always > tested -- > > the search path for referenced projects includes the current > folder. > > (david) > > Your first entry looks correct, except for the double > backslash. > > The key NAME is the basic file name including the extension but > > no path. Its string VALUE is the full path. So in your > notation, > > I would suggest something like: > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPa > > ths] > > "Db1.mdb"="C:\Db1.mdb" > > - Steve > in > > > I've been off line for a week. > > > I've been testing on WinME, using A97 SR2 > > > This is my registry setting: > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\RefLibPa > > ths] > > > "DB1.mdb"="C:\\DB1.MDB" > > > "db1"="c:\\db1.mdb" > > > "c:\\capix\\db1.mdb"="c:\\db1.mdb" > > > db1 is the project name, > > > DB1.mdb is the file name > > > c:\\capix\\db1.mdb is the fullpath to the original MDE. > > > (Out of desperation I tried all three, because the first > didn't > > work) > > > c:\\db1.mdb is the new location of project db1 > > > --------- > > > do you notice anything wrong? > > > what operating system(s) have you tested with? > > > --------- > > > (david) > > > > The RefLibPaths registry entry does work in Access 97. > > > > In my case, I distribute a front-end compiled .Mde, with a > > > > reference to a compiled library .Mde, using the ODE > > installer. At > > > > install time, the users install to any drive or directory > of > > > > their choice, but I make sure there is a RefLibPaths entry > in > > the > > > > registry for my library compiled .Mde, using the ODE setup. > > The > > > > front-end compiled .Mde does successfully find the library > > when > > > > the user runs the application. > > > > - Steve > wrote > > in > > http://www.--.com/ > > > > at my > > > > > Except that you repeat the story about Access first > > checking > > > > for RefLibPaths > > > > > in the registry. That was in the A97 documentation > > (hidden - > > > > not in the index) > > > > > and is now in the A2K documentation. Did you ever get it > > to > > > > work with A97? > > > > > Have you ever tested it with A2000? Note that the A97 > > > > documentation > > > > > specifically referred only to VB projects in mdb, mde, > > mda. - > > > > which is what I > > > > > tried to do. > > > > > (Also, note that although A97 could 'find' mde's in the > > current > > > > directory, it > > > > > could not reliably 'use' them. I am not sure to what > > extent > > > > this depended on > > > > > the operating system, service pack, or use of mde instead > > of > > > > mdb.) > > > > > (Also, note that it checks memory before it checks the > > current > > > > directory -- > > > > > in Win98 if you try and run multiple copies of your > > application > > > > from different > > > > > directories, A97 will try to use the MDE copy in memory > > rather > > > > than the MDE > > > > > copy in the local directory if the MDE is not in the > > referenced > > > > path. So how > > > > > does this work in Win2K? Do separate copies get > separate > > > > environments, > > > > > in which case the already loaded MDE's will not be used?) > > > > > (david) > message > > > > > > Why it matters if you create a new DB is that > references > > are > > > > at a database > > > > > > level. Creating a new database starts it with "fresh" > > > > references. > > > > > > If you're not using specific references, remove them > from > > the > > > > list. If > > > > > > Access can't find one of the references, it affects its > > > > ability to use any > > > > > > of the references. > > > > > > For far more than you could ever want to know about > this > > > > problem, check out > > http://www.--.com/ > > > > at my > > > > > > homepage. > > > > > > HTH > > > > > > -- > > > > > > Doug Steele, Microsoft Access MVP > > > > > > http://www.--.com/ > > > > > > When this first happened I suspected a version problem, > > so I > > > > re-installed > > > > > > Access > > > > > > on the laptop from the same CD as the home computer, > but > > the > > > > problem still > > > > > > exists. > > > > > > And why does creating a new DB solve the problem? > > > > > > The DAO reference is checked on the laptop (I'm not at > > home). > > > > > > When I look at the References list in both databases > (on > > the > > > > laptop), they > > > > > > are not > > > > > > the same! But the DAO reference is 3.5 in both. > > > > > > The home-DB opened on the laptop shows 2 missing > > references: > > > > > > ProtoView Time Control > > > > > > Lead Control Module(8.0) > > > > > > I'm not using anything from either of those, and > neither > > is > > > > referenced by > > > > > > the > > > > > > laptop-DB (those aren't even on the references list) > > > > > > Dennis Glaeser > > > > > > -----Original Message----- > > > > > > It's a missing reference. If you're not using any > custom > > > > controls or > > > > > > automation, the most likely culprit is probably the DAO > > > > reference. Access 97 > > > > > > shipped originally with DAO 3.50, while later service > > > > releases introduced > > > > > > DAO 3.51. > > > > > > Open any module, or hold down the Ctrl key while > pressing > > G > > > > to open the > > > > > > Immediate window, and select References from the Tools > > menu. > > > > Look for any > > > > > > marked 'missing'. If it's the DAO reference, unselect > the > > one > > > > marked missing > > > > > > and select the version that is installed on that PC. > But > > > > you'll have to do > > > > > > it again the next time you move the database from once > PC > > to > > > > the other. For > > > > > > a more permanent fix, make sure both PCs are at the > same > > > > service release > > > > > > level. > > > > > > -- > > > > > > Brendan Reynolds > > > > > > http://www.--.com/ > > > > > > I have Access 97 both at home and at work. I have a > > database > > > > application, > > > > > > with > > > > > > code, which I copied from home to my work laptop. When > I > > run > > > > the > > > > > > application on > > > > > > the laptop I get a "cannot find project or library" > > message > > > > and the de{filter} > > > > > > identifies a string function (LEFT in this case). The > > Help > > > > button has me > > > > > > try to > > > > > > find add-ins which may not be present. > > > > > > Now the strange part. If I create a new blank DB on > the > > > > laptop and copy all > > > > > > the > > > > > > tables, queries, forms, reports, and modules to the > blank > > DB, > > > > IT RUNS > > > > > > FINE!!! > > > > > > I've looked everywhere I can think of to find where or > > why > > > > the home-DB > > > > > > doesn't > > > > > > work on the laptop. Bye the way, the laptop-DB works > > just > > > > fine on the home > > > > > > computer. > > > > > > Any suggestions? > > > > > > .
Wed, 17 Dec 2003 17:25:12 GMT

Page 1 of 2

[ 23 post ]

Go to page: [1] [2]