home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1993 #3 / NN_1993_3.iso / spool / comp / os / mswindo / programm / tools / 2217 < prev    next >
Encoding:
Text File  |  1993-01-24  |  1.5 KB  |  45 lines
  1. Newsgroups: comp.os.ms-windows.programmer.tools
  2. From: chris@chrism.demon.co.uk (Chris Marriott)
  3. Path: sparky!uunet!pipex!demon!chrism.demon.co.uk!chris
  4. Subject: Re: DLL from Visual Basic to Access 
  5. Distribution: world
  6. References: <1993Jan23.072957.26531@henson.cc.wwu.edu>
  7. Organization: None
  8. Reply-To: chris@chrism.demon.co.uk
  9. X-Mailer: Simple NEWS 1.90 (ka9q DIS 1.19)
  10. Lines: 30
  11. Date: Sat, 23 Jan 1993 17:39:44 +0000
  12. Message-ID: <727810784snz@chrism.demon.co.uk>
  13. Sender: usenet@demon.co.uk
  14.  
  15. In article <1993Jan23.072957.26531@henson.cc.wwu.edu> n9148984@henson.cc.wwu.edu writes:
  16.  
  17. >Very simple question.  What Dll can one use to start up MS Access
  18. >from Visual Basic.
  19. >
  20. >
  21.  
  22. No need to use a DLL at all.  Just use the Windows "WinExec" API to start
  23. it.  ie,
  24.  
  25.     WinExec( "access.exe", 1 )
  26.  
  27. assuming that Access's file name is "access.exe" (which I don't actually
  28. know!).
  29.  
  30. I have to admit that I don't use VB, but from reading this newsgroup I get
  31. the impression that you can call Windows API functions from it.
  32.  
  33. Best wishes,
  34.  
  35. Chris
  36.  
  37. -- 
  38. --------------------------------------------------------------------------
  39. | Chris Marriott                           | chris@chrism.demon.co.uk    |
  40. | Warrington, UK                           | BIX: cmarriott              |
  41. |                                          | CIX: cmarriott              |
  42. | Save the whales.  Collect the whole set. | CompuServe: 100113,1140     |
  43. --------------------------------------------------------------------------
  44.  
  45.