.NET equivalent commands in Access VBA

  • Thread starter Thread starter Microchip
  • Start date Start date
M

Microchip

I have an ASP.NET file which writes to an application on the same machine
using sockets. But I need to do this in Access rather than a webpage.
1. Can I use .NET commands in Access?
2. Are there equivalent libraries available to Access that provide the same
functions?

The problem I am trying to solve is sending an XML file to a client
application ( via 127.0.0.1 and a specific port) which forwards the file to
its own server, then receives back a response which I need to read.
 
On Wed, 15 Jul 2009 02:50:01 -0700, Microchip

No.
No.

You may be able to use the XMLHTTP object to do that.

-Tom.
Microsoft Access MVP
 
Where is the Access backend database loaded? Given that ASP.NET can access
and read/edit/delete records in a database, you could use ASP.NET to lookfor
and read the file.
 
Thanks for the response. The data and frontend code are in the same local
db. The .NET commands I need create a socket through which to access a local
client to a server elsewhere. I suppose I could access the .net dll from
within Access?
 
Thanks Tom, I'll research taht and try it.

Tom van Stiphout said:
On Wed, 15 Jul 2009 02:50:01 -0700, Microchip

No.
No.

You may be able to use the XMLHTTP object to do that.

-Tom.
Microsoft Access MVP
Click to expand...
 
I suppose I could access the .net dll from
within Access?
Click to expand...

Doesn't work like that (unfortunately). VBA cannot be a host to .NET

I think what Dave was saying was rather than using an Access frontend, use a
front end such as asp.net that has the capability to connect to an Access
backend. Your database should be split anyway.




--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
 
Ding! Ding! Ding! Give the man a cupie doll.

The commonly accepted rule is that the user interface and data in an Access
based application should be split with the backend sitting on a shared
resource somewhere and the frontend on the local machine. If your webserver
and fileserver are one and the same, the ASP.NET application can access the
backend just like it was a regular front end doing whatever work needed to be
done. Even if you have two different machines for the webserver and
fileserver, as long as they're on the same network, ASP.NET can still reach
out to the fileserver and access the data. It also, quite nicely, lays the
ground work to publish the data to your company's intranet for those users
who don't have, or need, the Access front end.
 
Thanks for your responses everyone.
Efectively, the database is already split in that some of the data I read is
in other database files. Unfortunately, I'm developing just a small part for
someone else and have no control over where the data, frontend and other
services will reside.

I have the external connection running in java and running it by hand in a
command prompt. I think I can call a command prompt from within Access so I
should be able to run the java code that way. But what a kludge!

Thanks again gents.

Microchip
 
The true cost of software is not the cost to build it, but rather the cost to
maintain it.

Although you can certainly launch independent programs via Access, I would
stay away from that if at all possible since there's no way to have the two
communication with each other.

In a split database, the ONLY data that should ever reside in the front end
should be temporary data that is specific to the particular user using it, if
that.

You may need to sit down with the other person and have a come to Jesus talk
with them about the overall design.
 
I did this miss this in the original post...

You can have Access launch a web page which if its an .aspx page would
effectively execute whatever code needs to run.
 
Back
Top