Note: the attached project contains CLASSIC asp scripts and NOT asp.net scripts.
I have a propriatary PC app that uses MSAccess.
The author is good enough to leave the MSAccess .mdb tables unsecured.
Where he gives free access to the table layout and the data contained there in.
... i.e. the data belongs to his clients.
But there are NO queries or reports etc available.
I've asked multiple times for web access ( and now mobile access )
but it seems its too expensive, too complex, or not requested by enough clients.
So I've decided to do it myself.
My apps are for me, my family and friends, and designed for HTC HD2.
And I have no intention of selling in any way shape or form.
--
I tried to start with a web solution only via phone browsers but found I didn't know enough about web languages to control the width of the screen enough for all android sizes etc.
And I really didn't want to learn yet another language.
----
As far as I know I CAN'T access a remote MSAccess .mdb directly from Android via B4A.
So I have to use a web server.
I already have IIS 5.1 already setup and working.
I use simple DNS plus to redirect m.com to my IIS server (192.168.1.2)
which is just the familys main web page
The m.com is short for mobile.com
I wanted just m but the phones can't handle just m so its m.com.
--
I've found that I get better / faster response from all my computers and phones when they have a static IP Address.
i.e.
Router:
192.168.1.1
MyMainComputer:
192.168.1.2
where simple DNS plus is running
Default Gateway of 192.168.1.1
and DNS1 of 192.168.1.2
Any other computers or phones:
192.168.1.x
Gateway of 192.168.1.1
and DNS1 of 192.168.1.2
--
Attached to this post is a b4a project HttpUtils2WithASP.b4a
The only thing in this b4a project that actually relates to CLASSIC ASP is the
PostString call to an asp script on my IIS 5.1 web server:
--
Also in the Files folder is some very simple asp scripts like HelloWorld to make sure CLASSIC ASP is working.
And a very simple asp script that opens a MSAccess .mdb and validates a UID and PW.
--
This should be an easy enough start to get us into all kinds of trouble.
Can't express enough how easy it was with HTTPUtils2 and examples.
..
I have a propriatary PC app that uses MSAccess.
The author is good enough to leave the MSAccess .mdb tables unsecured.
Where he gives free access to the table layout and the data contained there in.
... i.e. the data belongs to his clients.
But there are NO queries or reports etc available.
I've asked multiple times for web access ( and now mobile access )
but it seems its too expensive, too complex, or not requested by enough clients.
So I've decided to do it myself.
My apps are for me, my family and friends, and designed for HTC HD2.
And I have no intention of selling in any way shape or form.
--
I tried to start with a web solution only via phone browsers but found I didn't know enough about web languages to control the width of the screen enough for all android sizes etc.
And I really didn't want to learn yet another language.
----
As far as I know I CAN'T access a remote MSAccess .mdb directly from Android via B4A.
So I have to use a web server.
I already have IIS 5.1 already setup and working.
I use simple DNS plus to redirect m.com to my IIS server (192.168.1.2)
which is just the familys main web page
The m.com is short for mobile.com
I wanted just m but the phones can't handle just m so its m.com.
--
I've found that I get better / faster response from all my computers and phones when they have a static IP Address.
i.e.
Router:
192.168.1.1
MyMainComputer:
192.168.1.2
where simple DNS plus is running
Default Gateway of 192.168.1.1
and DNS1 of 192.168.1.2
Any other computers or phones:
192.168.1.x
Gateway of 192.168.1.1
and DNS1 of 192.168.1.2
--
Attached to this post is a b4a project HttpUtils2WithASP.b4a
The only thing in this b4a project that actually relates to CLASSIC ASP is the
PostString call to an asp script on my IIS 5.1 web server:
B4X:
Jobx.PostString("m.com/b4a/myB4AScript.asp")
Also in the Files folder is some very simple asp scripts like HelloWorld to make sure CLASSIC ASP is working.
And a very simple asp script that opens a MSAccess .mdb and validates a UID and PW.
--
This should be an easy enough start to get us into all kinds of trouble.
Can't express enough how easy it was with HTTPUtils2 and examples.
..
Attachments
Last edited: