Nicholson, Karen
cyx5 at cdc.gov
Wed Mar 16 12:10:25 CST 2005
I haven't tried the detect and repair... But this is the function.
Public Function fcnBldFileSelect _
(strInitDir As String, strFileTitle As String, bolRepeat As Boolean,
intDialogType) _
As String
'******************************************************
'* Build File Select Dialog Box
'* '*
'* Purpose: This function creates a file dialog box
'* that allows the user to select a single
'* file. The default file type is ".mdb"
'* However, the "All Files" option is also
'* allowed.
'*
'* Notes: This function requires the loading of the
'* Microsoft Office 10.0 Office Library.
'*
'* Call Line:
'* strInitDir: String Variable containing the
'* initial file path to search.
'* strFileTitle: String Variable containing the
'* text of both the file dialog
'* title and the message box if
'* a file MUST be selected.
'* bolRepeat: Boolean Variable indicating
'* whether a file MUST be chosen.
'* intDialogType: Integer Variable containing a
'* valid msoFileDialog Type
'*
'* Modifications:
'*
'******************************************************
'Declare a variable as a FileDialog object
Dim fdialog As Office.FileDialog
'Create a FileDialog object as a File Picker dialog box.
Set fdialog = Application.FileDialog(intDialogType)
'Declare a variable to contain the path.
Dim vrtSelectedItem As Variant
FileLoop:
With fdialog
'Allow user to make only one selection in the dialog box
.AllowMultiSelect = False
'Set the path where the file dialog should initially start
.InitialFileName = strInitDir
'Set the title string of the file dialog box
.Title = strFileTitle
If intDialogType = msoFileDialogFilePicker Then
'Clear out the current filters, and add our own.
.Filters.Clear
.Filters.Add "Access Databases", "*.MDB"
.Filters.Add "All Files", "*.*"
End If
'Use the Show method to display the File Picker dialog box and
return the user's action.
'If the user presses the action button...
If .Show = -1 Then
'Step through each string in the FileDialogSelectedItems
collection.
For Each vrtSelectedItem In .SelectedItems
fcnBldFileSelect = vrtSelectedItem
Next vrtSelectedItem
'If the user presses Cancel...
Else
fcnBldFileSelect = "False"
End If
End With
'Release the File Dialog variable.
Set fdialog = Nothing
End Function
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Wednesday, March 16, 2005 12:49 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] MSO.DLL He--
Because that's the one you installed last. Have you tried a detect and
repair on Access XP to see if that fixes it? What do you need the
Office library for? You may be able to use something else as an
alternative.
Charlotte Foust
-----Original Message-----
From: Nicholson, Karen [mailto:cyx5 at cdc.gov]
Sent: Wednesday, March 16, 2005 9:40 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] MSO.DLL He--
I have the full version of office 10, XP, installed.
The ITSO installed just plain old Access 2003 for me, office 11. I am
developing in XP. The Microsoft Office 10.0 is not in the references.
I point to the location and it does not come on board. The one from the
office 11 is there.
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Wednesday, March 16, 2005 12:31 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] MSO.DLL He--
You should not have a problem if you have both installed. You said you
did NOT have the Office 10 dll installed, but how could you not if you
have Access XP installed? Are you using 2003 to develop for XP or what?
Charlotte Foust
-----Original Message-----
From: Nicholson, Karen [mailto:cyx5 at cdc.gov]
Sent: Wednesday, March 16, 2005 8:25 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] MSO.DLL He--
Darn. So I can not develop in my version of XP now for others with XP
because I also have 2003 installed. I have to take the in between step
and go to a PC that does not have 2003 installed and change the
reference or distribute .mde's. An mde is not a bad idea. I will have
to think on that.
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Wednesday, March 16, 2005 11:03 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] MSO.DLL He--
It will ALWAYS read Office 11 version on your machine. Unless you're
distributing an MDE, it should resolve itself on the other machines. If
it doesn't, then go to a machine with Office 10 installed and set the
reference there. Then distribute copies of that one.
Overwriting will most likely break your Office 11.
Charlotte Foust
-----Original Message-----
From: Nicholson, Karen [mailto:cyx5 at cdc.gov]
Sent: Wednesday, March 16, 2005 5:36 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] MSO.DLL He--
I tried to do that, but my references don't update, it still reads
Office 11 version. Would it kill something if I just took the one from
the office 10 folder and overwrote the one in the office 11 folder?
Warning warning, idiot approaching?
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: Wednesday, March 16, 2005 8:26 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] MSO.DLL He--
Karen - You'll need to use the Browse button in the references dialog
box to select the correct file. It's in the Office10 folder, but I
don't know the file name. The ridiculous references dialog box won't
show the full path.
Dan Waters
ProMation Systems
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson,
Karen
Sent: Wednesday, March 16, 2005 6:49 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] MSO.DLL He--
I just love .dll's. I now have Access 2003 installed on my PC, and
Access XP and Access 2000. The applications I develop for in-house are
AccessXP. Moving right along, I set a reference to Microsoft Office
11.0 Object Library in an AccessXP database and sent it up to the server
to deploy. Since my users don't have Access 2003 installed, they do not
have the MSO.DLL for 11.0 so they are bombing out. Trouble is, I don't
have Microsoft Office 10.0 available in my references anymore and see
that this file is named the same in both versions. Anybody know how I
can get the 10.0 version back in my references list?
Feels like a Monday.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com