Kallal Albert D. Kallal I would never use this, as I fear they'll do the same thing they did with the FileSearch Object, and take it out of a future version. Since I have the direct API code in place already, there's not much need for me to use a wrapper like this, though certainly it would avoid the bit code conversion problem with the API code. FileSearch don't believe was included with runtime and thus could not always be assumed.
FileDialog been there since access , always worked with the runtime, and works without having to set any references late bind. The dialog is part of all of office and works in 64 bit edition as you noted. I do agree it could be removed, but so far historically this choice would have worked since with less hassles then the api and this includes the new 64 bit version.
I quite much adopted this, and if I eat crow on this, I will do so in public, but I think it is the best choice right now. The FileSearch object was a member of the Access Application object, so it required no reference. I suspect it is available in the runtime, given that it's a member of the top-level Application object.
So far as I can tell, it was implemented identically to the way FileDialog is implemented, and yet it was removed in A I think that's because MS wanted to replace their old search techniques with ones based on the new search infrastructure, so it was more politics than anything else. I admit it's hard for me to imagine a similar politically motivated reason to remove FileDialog.
This does not work with MS Access 64 bit. When I run the code above with a reference to the Microsoft Object Adding "Microsoft Office Thank you for posting that solution Albert!
Add a comment. Tony Toews Tony Toews 7, 1 1 gold badge 20 20 silver badges 26 26 bronze badges. The code in the link you posted will probably work, but it's oh-so-messy. And the real WTF is the use of the Variant type. There's just no excuse for that when you don't absolutely have to use it.
The code Tony cited doesn't work? I've got it working on bit Win7, and it's never been an issue -- it worked without alteration the first time it was called. The code Tony cited does not even compile on Access 64 bit version. Even after adding the PtrSafe attribute it does not work. It will certainly work with Access 32 bit version under Windows 7 64 bit. I was working with this problem for a long while Max Albanese Max Albanese 31 1 1 bronze badge. David, I saw the long pointer article above earlier and attempted to make Tony's code work.
Sorry this didn't help. Thanks for your feedback. MVP Moderator Many thanks for prompt reply and valuable time. However I respectfully disagreepartly. RE: This is by design. No MS does not design bugs. My users lose their valuable edits. This needs to be fixed by a patch. RE: Users will get what they deserve:Users are customers and deserve the best value for money and their faith in us.
Re: no picture added, and a bad review from their manager :- : This is not relevant in a technical form like this.. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
The Northwind. Click the All tab, click Name , typeText1, and then close the Properties dialog box. Right-click the label control that is associated with the Text1 text box, click Properties , and then click the All tab. Click Caption , type Text1, and then close the Properties dialog box. Add a command button to Form1 , right-click the command button, click Properties , click Name , type Command1, click Caption , and then type Command1.
On the Insert menu, click Module , and then insert the following code into Module I am trying to allow the user the capability to browse to a file to import that file into access. I found code for it, but it still does not work.
I can't find the reference that is recommended. Local time Yesterday, Joined Mar 5, Messages 1, Are you using the 64 bit edition?
Some API calls don't work in the 64 bit edition unless you use the appropriate call. Local time Today, Joined Dec 23, Messages Hi dferreira, In the past, we used Windows API to callup the common dialog box in order to obtain a filepath.
This has become problematic with 32 and 64 bit versions of windows. You may have difference version number instead of Thank You, Thank You!!!!!! I have spent so much time tring to make this work!
If you were here I would kiss you! You are welcome - we are all here to help! I was tearing my hair out using comdlg Come back here if you have any problems. Can someone tell me how to import the file using the File Dialog now that I have that code working. Local time Yesterday, Joined Dec 15, Messages I would love detailed instructions in how to make this work. Copy and paste to module means nothing to me. Hi ulieq and dferreira, Thanks for bumping the thread. Apology for my absence.
0コメント