Search results for query: *

Glenn9999, Yes I use the stdcall as follows: Procedure CloseDlg(DlgStage : Integer); StdCall; begin TDialogDestroyer.Create(DlgStage); end; As I mentioned in my initial post, the entire process works perfectly on my own development machine (Windows XP Pro with Microsoft Access 2000), so I...

Glenn9999 Thank again for your continued help. Whilst I coded the dll using Delphi 7.0, as I mentioned in my initial posting, the dll is being called from within a Microsoft Access database, so using VBA code. I believe the dll will be loaded at program start-up.

Glenn9999 Thanks for your reply. There are no error messages of any kind. The dll is meant to search out a dialog box and click a button on it. The dll is linked dynamically. I didn't think you could statically link a dll (hence the name)??

whosrdaddy, Thanks for your reply. Access 2000 is installed on the server, so the MDAC components should already be in place.

I developed a dll using Delphi 7.0. I call the dll from a Microsoft Access database. On my own machine, running Windows XP Pro and Microsoft Access 2000, the dll works precisely as intended, however when I place it on the server it was designed to work on, nothing appears to happen. The server...

I'm very much a Delphi beginner, so please feel free to tear my poor 'newbie' coding to pieces (good or bad, it will all help). I am trying to write code to close Outlook security dialog boxes. The ultimate intention being to create a dll which I can then call from Microsoft Access using VBA...

rkasnick, As yet I haven't done any Email related coding. I guess this was a somewhat rare example of decent forward planning - enquiring about somethign more than 5 minutes before you need it. I will be starting work on the Email functionality quite soon and I plan to try the Ostrosoft...

Oops, just as well you mentioned that Ed, I'd forgotten about the ability to award stars. Now taken care of, thanks again Carl. I'll look forward to any other feedback you may be able to offer on the components. Cascot

Hi Carl, Thank you so much for pointing me to the website for these components. They look very promising. Have you had an problems with them, any apparent bugs, or anything else of note? Thank you again for your help. It is much appreciated. Cascot

Rick, Before exploring any other possibilities I would have to suggest a straightforward uninstall, reboot, and re-install of Office 2003 Professional.

Ed2020, Thanks for your reply. The ultimate aim is to distribute the application so the Email clients of the end users can't be known for sure. Yes it would be possible to make something like Outlook Express a requirement, but I would rather have the program function as independently as...

I am shortly going to need to incorporate Email functionality into an Access 2003 application. Ultimately this application will become a runtime. I mention that as it may have an impact on possible solutions, though from what I understand, programs such as SageKey can greatly reduce the problems...

hneal98, Thanks for your reply. Unfortunately this is a system that has been used in anger for many years and I do not have the option of being able to amend the user interface to that extent just because of the upgrade to Access 2000.

I have an application originally designed in Access 97 which I recently converted to Access 2000. Some forms have two pages using a pagebreak. Everything worked as expected in Access 97, however since converting to 2000 there now seems to be a problem related to the use of [ObjectName].SetFocus...

I couldn'd find any alternative approaches that involved sticking with the use of the LinkMasterFields and LinkChildFields properties, so I ditched those entirely and went with the following... - I still have only one Subform object - The RowSource of each form that will be opened within the...

alvechurchdata, Thanks for your reply. I'm not sure quite yet, but I think that approach may still suffer from some of the same problems. For example when a subform is hidden would it already have it's SourceObject defined? If it did then there would be the problem of what to set the subform's...

I have a subform object that, depending on user input, will display one of several forms. Two are continuous list-type forms, the others display details of a single record. My problem is that using the SourceObject, LinkMasterFields and LinkChildFields properties of the subform doesn't seem to...

PHV, I thought that in such cases simply not assigning a value was the equivalent of Null and thus you didn't actually have to assign a Null to the field, it just didn't have a value set at all thus leaving it as Null. But maybe that is incorrect.

There's also the Nz function which can be used to test a variable of type variant and return a specific value if it's value is null. For example... DiversLic = Nz([Text24],"") Which will either assign the value of Text24 or "" if Text24 is Null.

PHV, Absolutely true. Like I said "in general". The majority of the time you should be able to avoid scenarios where you actually need to assign a Null value.