[AccessD] Screen Scraping - GUI-less Mode on Windows Server 2012

Gustav Brock gustav at cactus.dk
Mon Jul 27 11:30:44 CDT 2015


Hi Brad

The remote machine does not go into a non-GUI mode, it just logs of from the session - as if you worked at the machine and chose to logout.

So if your application needs to operate in a logged-in GUI session - and Access does that - you somehow must maintain a logged in session.

The alternative is to have your application running as a service. That can be prommed in C#, C++, VB.NET or other programming language but not Access.

/gustav

________________________________________
Fra: AccessD <accessd-bounces at databaseadvisors.com> på vegne af Brad Marks <bradm at blackforestltd.com>
Sendt: 27. juli 2015 18:11
Til: Access Developers discussion and problem solving
Emne: [AccessD] Screen Scraping  - GUI-less Mode on Windows Server 2012

All,

I have an application that pulls data from a purchased manufacturing system and then feeds this data into a purchased accounting system.

The only way to feed data into the purchased accounting system is via the screens/forms provided by the package.

The application that I built uses Access 2007 to pull the data from the manufacturing system and a scripting tool called AutoHotKey to do “Screen Scraping” to feed the data into the accounting system via the accounting system’s screens.

This method works, but it is not ideal.

I used AutoHotKey to do the screen scraping because I knew how to use this tool to do this and because I was not sure if Access could be used to easily read and write screens from another application.

Is it possible to do this with Access?



My second question is a bit more complicated.

This application has been running successfully every night for about 6 months.  It runs in unattended mode.  It runs on a server (Windows 2012).

Currently, in order for this application to run, I need to be connected from a desktop PC via Remote Desktop to the server.  If this connection is lost, the application will not run.

As I understand it, the server goes into “GUI-less” mode when the remote desktop connection is lost.  Therefore, I currently keep a remote desktop connection from my desktop PC to the Server all of the time.

This works, but I do not like the need to have the remote desktop connection available all of the time.

If the desktop PC goes down or is rebooted, the remote desktop connection is lost and needs to be re-established.

I am not very familiar with the idea of the “GUI-less” mode on the server.  I wonder if there is a way to prevent the server from going into GUI-less mode when the remote desktop connection is lost.

Has anyone else ever run into anything like this?

Any suggestions on how to improve this situation?

Thanks,

Brad


More information about the AccessD mailing list