Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LINKED DB FOR REPORTS NOT WORKING

Status
Not open for further replies.

baudouxnorthrup

Technical User
Feb 19, 2003
16
US
I created a db for incidents. Because there is alot of users and our managers want to be able to view reports frequently, I created a 2nd db that links the maintable from the original db.

In this new db, I created a report that lists current day and 3 subsequent days worth of incident reports.

I put the shortcut on my desktop. Then I emailed it to my boss. He clicks on it, and he isn't able to open the database. It just hangs out there not returning anything, or it will act like it is looking for the db and gives a message that the 'shortcut missing'. I have both the original db and the linked db in a lanshare that is open access to everybody at the plant so lanshare access can't be the key to this.

Why is my boss not able to open the linked db to view the reports?

It is really frustrating me to what may be happening.
 
Check the References on your boss' machine. See if he/she is missing any.
 
FancyPrairie, how do I check his references on his PC?

I also have my coop who cannot access the linked db.
 
If they have the full blown version of Access on their machine, then open a module in design view and goto Tools|References. That will list all of the References and tell you which ones are missing. If they don't have the full blown version, then you will have to look at them on your machine, note the name of each file (dll) and then check to see if that file exists on the their machine. (There are other ways to do it, but, for now, that's the easiest).

Note that I'm not saying that this is the problem. It's just a start in trying to determine the problem.
 
I ran into something similar awhile back....can't explain why, but it seems that when I emailed the shortcut, it had profile specific info embedded. What I did was to email a hyperlink to verify the problem and eventually sent out instructions to users with UNC path to set up their own shortcuts.
 
Rick39......I think the UNC path thing is my problem. How do I find what my UNC path should be so I can send out instructions for others to set up their own shortcuts?

This bit of info may be the lifesaver of the day for me. My performance review is at 1pm today. Nothing would be greater than resolving this just before that review.
 
What do I do with it? Do I put it in a macro in my db to find the UNC?
 
Rick39, may be on the right track. Your machine may have the server mapped to F drive, but you boss' machine may have it mapped to I drive. Therefore, it wouldn't work.

The best way to set it up is to setup a share name. Then link your tables using the share name (rather than a drive letter) and your short cut should also point to the share.
 
Paste the following into a new module, then run getNetPath:

' 32-bit Function version.
Declare Function WNetGetConnection32 Lib "MPR.DLL" Alias _
"WNetGetConnectionA" (ByVal lpszLocalName As String, _
ByVal lpszRemoteName As String, lSize As Long) As Long

' 32-bit declarations:
Dim lpszRemoteName As String
Dim lSize As Long

' Use for the return value of WNetGetConnection() API.
Const NO_ERROR As Long = 0

' The size used for the string buffer. Adjust this if you
' need a larger buffer.
Const lBUFFER_SIZE As Long = 255
Sub getNetPath()
Dim DriveLetter As String
Dim cbRemoteName As Long
Dim lStatus As Long

DriveLetter = UCase(InputBox("Enter Drive Letter of Your Network" & "Connection." & Chr(10) & "i.e. F (do not enter a colon)", "Find Network Path..."))
DriveLetter = DriveLetter & ":"

cbRemoteName = lBUFFER_SIZE ' Specifies the size in charaters of the buffer.
lpszRemoteName = lpszRemoteName & Space(lBUFFER_SIZE) ' Prepare a string variable by padding spaces.
lStatus& = WNetGetConnection32(DriveLetter, _
lpszRemoteName, cbRemoteName)
' Return the UNC path (\\Server\Share).

If lStatus& = NO_ERROR Then ' Returns 0 (NO_ERROR) if succesful.
MsgBox lpszRemoteName, vbInformation, "Path Found"
Else
MsgBox "Unable to obtain the UNC path.", vbInformation, "Error"
End If

End Sub
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top