[AccessD] API calls crashing

Gustav Brock gustav at cactus.dk
Tue Feb 3 09:58:37 CST 2015


Hi Andy

You may of course try other things first. Clean the machine (Crap Cleaner is my favourite), reinstall Access and the application, but often you just end up wasting a couple of hours on nothing.

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Andy Lacey
Sendt: 3. februar 2015 16:52
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] API calls crashing

Thanks Gustav. Was rather hoping to avoid that. If possible I'd like to understand why, what might cause the problem, in case this happens again.
 

> On 03 February 2015 at 15:30 Gustav Brock <gustav at cactus.dk> wrote:
>
>
> Hi Andy
>
> If the application runs on other (similar) machines, the error should 
> be found in the OS install.
>
> If you can't find out what - I guess you can't - request a reinstall 
> of that machine.
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] På vegne af Andy Lacey
> Sendt: 3. februar 2015 16:06
> Til: Access Developers discussion and problem solving
> Emne: [AccessD] API calls crashing
>
> I am totally at a loss on this.
>
> My big Access 97 app (I know, I know, but it works) is crashing on one 
> machine, a machine it has run on for years. I've tracked it down to API calls.
> Any time it calls a Kernel32 API it just exits - no message, no 
> nothing, just closes. Now it's perfectly possible that central ICT 
> here have installed or updated something overnight which has 
> interfered, in fact I can only think that must have happened. Question is, what can I do about it?
>
> This is a typical api call which crashes out:
>
> Private Declare Function apiGetComputerName Lib "Kernel32" Alias _ 
> "GetComputerNameA" (ByVal lpBuffer As String, nSize As Long) As Long
>
> I know I could use Environ to get the computer name but that's not the point.
> There are lots of similar calls and they're all failing.
>
> Help please.
>
> Andy
>
> --
> 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



More information about the AccessD mailing list