Locking a database from a non paying client
-
- Administrator
- Posts: 78880
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Locking a database from a non paying client
The SQL Server database should not be on a computer owned or controlled by the client - the client's front end would contact it over the internet.
Best wishes,
Hans
Hans
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
By what means would the Client's FE contact it over the internet?
-
- 3StarLounger
- Posts: 331
- Joined: 11 Feb 2010, 03:55
- Location: Land O Lakes, FL
Re: Locking a database from a non paying client
It would be my SQL Server or a MySQL server, sitting anywhere. Could be on a website. Ideally you'd have a Stored Procedure which returned the information, which you'd call via a PassThrough query (including the ClientID as a parameter).
Mark Liquorman
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
Thanks Mark, but i have never written a Stored Procedure.
Can a stored procedure access the web?
Where can i read up on Stored Procedures?
Would the pass through query in the Clients FE access the SQL Server stored procedure. I still am trying to understand this approach never having used Pass Through queries. Would the client's FE have a link to a SQL Server table on a server somewhere?
As you can see i have no idea about this.
Can a stored procedure access the web?
Where can i read up on Stored Procedures?
Would the pass through query in the Clients FE access the SQL Server stored procedure. I still am trying to understand this approach never having used Pass Through queries. Would the client's FE have a link to a SQL Server table on a server somewhere?
As you can see i have no idea about this.
-
- 3StarLounger
- Posts: 331
- Joined: 11 Feb 2010, 03:55
- Location: Land O Lakes, FL
Re: Locking a database from a non paying client
Stored Procedures are in the SQL Server database. You don't actually need to use it, you can just put the SQL in the passthrough query. A passthrough query has to have the connection parameters to the SQL Server (servername, databasename, user, & password).
Mark Liquorman
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
Land O Lakes, FL
see my website http://www.liquorman.net for Access Tips and Tricks, and for my Liquorman Utilities.
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
Would you provide an example of a passthrough query with those fields please.
-
- Administrator
- Posts: 78880
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Locking a database from a non paying client
I'm not sure this is going to work, but here is a description from Microsoft:
How to create an SQL pass-through query in Access
How to create an SQL pass-through query in Access
Best wishes,
Hans
Hans
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
Thanks I will try that, i need a ODBC database on the web somewhere to test it thoug
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
Would you give me an example of a connection string that specifies Servername, Databasename etc.Mark L wrote:A passthrough query has to have the connection parameters to the SQL Server (servername, databasename, user, & password).
I presume the servername is a unc type address?
-
- Administrator
- Posts: 78880
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Locking a database from a non paying client
Here is more information about connection strings than you'll ever need: ConnectionStrings.com.
Best wishes,
Hans
Hans
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
Thanks Hans i will look at that after breakfast.
I have had a look at that and you are right, there is way more information that i need to the point it's confusing. It doesn't mention all the keywords like "Server" or "Databasename", but at least i can work on from there.
I wonder if there is a link to all the keywords that are used in connection strings.
I have had a look at that and you are right, there is way more information that i need to the point it's confusing. It doesn't mention all the keywords like "Server" or "Databasename", but at least i can work on from there.
I wonder if there is a link to all the keywords that are used in connection strings.
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
I have found an interesting link via google:
http://www.connectionstrings.com/Articl ... g-keywords
http://www.connectionstrings.com/Articl ... g-keywords
-
- Administrator
- Posts: 78880
- Joined: 16 Jan 2010, 00:14
- Status: Microsoft MVP
- Location: Wageningen, The Netherlands
Re: Locking a database from a non paying client
That's on the same website that I mentioned.
Best wishes,
Hans
Hans
-
- 5StarLounger
- Posts: 1148
- Joined: 08 Feb 2010, 21:27
Re: Locking a database from a non paying client
So it is, i didn't notice that. I just went googling.
Thanks for your time Hans and enjoy the new decade.
Thanks for your time Hans and enjoy the new decade.