Uknown Code.

[ScottishFencer]

Hi There,

When I start a legacy database I see that some code is kicked off. I'm not sure what it does:

Option Compare Database
Option Explicit

' Declare necessary API routines:
Declare Function FindWindow Lib "user32" Alias _
"FindWindowA" (ByVal lpClassName As String, _
                    ByVal lpWindowName As Long) As Long

Declare Function SendMessage Lib "user32" Alias _
"SendMessageA" (ByVal hWnd As Long, ByVal wMsg As Long, _
                    ByVal wParam As Long, _
                    ByVal lParam As Long) As Long

What does this code do?

I've had a look through the MS help pages and can figure out that it is acessing "user32.dll"; quite why I can't figure out.

I am looking for the source of some odd behaviour I am getting with this DB. We have a finance section that deals with Direct Debits. So long as the direct debit(DD) run is performed on machine it works fine. If it is done on any other then it doesn't work. The way that the DB connects with the DD software is by placing file on a network share. It does this by using some fairly standard code:

DoCmd.TransferText acExportDelim, , "Q_BACSOutput", "R:\SFQCDBs\SSSFA\bacs\BACS.dat"

When we get to this line it crashes out. However - do it on the correct pc and everything is ok. My feeling is that there is some old legacy code that is locking this down. Any help would be appreciated.

 

[CautionMP]

[ol][li]These allow your database to find other applications ([tt]FindWindow[/tt]), and allow the database to talk to them ([tt]SendMessage[/tt])[/li][li]Does [tt]Q_BACSOutput[/tt] draw data from a non-Access data source? If so do the finance sections have ODBC connections/privledges to this data source that others dont't?[/li][li]Does the finance sections have access to a shared drive ([tt]R:\SFQCDBs\SSSFA\bacs\[/tt]) that others don't?[/li][/ol]

P.S. A more decscriptive subject will ensure a greater chance of response in the forum.

CMP

Funny thing about being unemployed, weekends don't mean quite so much, just means you get to hang out with your working friends. Primus

 

[BoxHead]

SF,

I'm not sure about the initial code. It looks like it's just filling variables for some later use.

The issue with the transfer text could be several things (from my head-banging-on-my-desk experience).

1. Do the users on the 'incorrect' PCs have access to that directory? Could they open a new Word document and save it to R:\SFQCDBs\SSSFA\bacs?

2. Is that location on the server mapped as drive 'R' on the failing machines?

3. Is the R-drive actually a server-accessible directory residing on the machine that can write to it? I ask because it seems a true server directory would have a double backslash.


HTH



When Galileo theorized that Aristotle's view of the Universe contained errors, he was labeled a fool.
It wasn't until he proved it that he was called dangerous.

 

[ScottishFencer]

First off, sorry about the title. It was hastily typed after a long day of banging my head against the wall.


I have figured out what that code is for - later on it is invoked to check for an instance of Excel. Why? No idea but it's a red herring as far as this is concerned.

Q_Bacsoutput is an Access query that pulls some data from a table. I tried to manually export the data to a txt file from the problem pc (in fact ANY pc apart from the one on which it actually works) and kept getting an error message about components being missing. I'll get the full error text tomorrow as I am typing this from home. This is not a problem with the installation of Office on these pcs as you can export other queries from other apps. It is just this app that is a problem.

R: is a communal drive that everyone has access to. I have double, triple, quadruple checked the privilages and everything seems fine. Yes it is mapped - all machines have this drive mapped. I'll check the drive path to see if it is an issue. It does work from one the one pc on which this app works. All pc can access this share.

I have a feeling that the issue resides on the; or to do with; 'working' pc. That is; there is some registry hack or pc of code - something that I'm missing.

I've verified the ODBC connections. They are fine. In fact the app can be used for other things...

It's all a bit weird.