...@leafe.com
Subject: Re: sql server connection
Have you considered the firewall port requirements involved for your clients
in the generally inadvisable process of exposing a SQL Server directly to
the internet?
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server
Have you considered the firewall port requirements involved for your clients in
the generally inadvisable process of exposing a SQL Server directly to the
internet?
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
___
Post Messages to: ProFox@le
y
concerns as well.
Thanks!
Paul H. Tarver
Tarver Program Consultants, Inc.
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Richard
Kaye
Sent: Thursday, February 11, 2021 12:05 PM
To: profoxt...@leafe.com
Subject: RE: sql server connection
Reall
I do this with multiple applications and we handle it using a DSN-less
connection. The only requirement for the pc is a 32-bit MS SQL ODBC driver
must be installed, but no DSN needs to be created on the computer. Also, you
must have SQL Credentials configured on the SQL Server as you cannot use
Win
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Richard
Kaye
Sent: Thursday, February 11, 2021 12:05 PM
To: profoxt...@leafe.com
Subject: RE: sql server connection
Really? All you have to do is set trusted=yes in the conn string, afaik. But
I could
And installing the 64 bit driver will include the 32 bit driver.
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Richard Kaye
Sent: Thursday, February 11, 2021 1:05 PM
To: profoxt...@leafe.com
Subject: RE: sql server connection
Really? All you have to do is set trusted=yes in
r/
--
rk
-Original Message-
From: ProfoxTech On Behalf Of Paul H. Tarver
Sent: Thursday, February 11, 2021 12:49 PM
To: profoxt...@leafe.com
Subject: RE: sql server connection
I do this with multiple applications and we handle it using a DSN-less
connection. The only requirement for the
Here is a powershell script example that will install the client on your
workstation(s).
https://www.server-world.info/en/note?os=Windows_Server_2019&p=mssql2019&f=4
I would skip ODBC at all costs and just use the client directly.
On Thu, Feb 11, 2021 at 8:17 AM Eric Selje wrote:
> Rafael,
>
On 02/11/21 9:20 AM, Rafael Copquin wrote:
Hi Vince
I understand your example. Actually I used it and my test worked like a
charm.
However, wouldn't it require that my clients have the SQL Server Native
Client version already installed in their computers?
Rafael
The drivers, yes, but those ca
Hi Eric, I was afraid they would need to install the driver. I'll try
innosetup as you suggest
In any case, thank you both, Eric and Vince
Best regards
Rafael
El jue, 11 feb 2021 a las 11:17, Eric Selje ()
escribió:
> Rafael,
>
> They'll have to have the driver installed in order to talk to SQ
Rafael,
They'll have to have the driver installed in order to talk to SQL Server.
The best way is to provide them with an Installer program (use InnoSetup -
free and easy) that installs your app as well as the driver. It can add a
DSN too, although you may want to consider hardcoding that connecti
Wow. Lots of stuff to check out there. Will definitely be checking out
the SQL server stuff even though I'm not writing the new software. I
could well be writing some reports though.
Thanks,
Peter Cushing
IT Department
WHISPERING SMITH
On 21/08/2019 14:40, Stephen Russell wrote:
> An ODBC co
An ODBC connection has to be created on every workstation, as well as
installing a SQL Client as well. I'd avoid the ODBC route and go straight
SQL Client that does have to be installed on each machine. Pick a higher
Client version number such as 10 or 11 today.
connectionString="Data Source=SE
Now got it working with SQLSTRINGCONNECT() thanks.
I will have a look at this native client. Does that give you any
advantages over the ODBC connection?
Also noticed in an archive post someone using this to check the
connection before doing a real query/update.
nResult=SQLEXEC(datahandle,'SELECT
I use SQL native client (which is an option to install when installing SQL
server):
https://www.microsoft.com/en-us/download/details.aspx?id=50402
And then I use a connection string like:
ConnectionString=DRIVER=SQL Server Native Client
11.0;Trusted_Connection=Yes;DATABASE=GoldBuy;SERVER=MySer
Make sure you are using ODBC Data Sources (32-bit) and in the Drivers tab
you'll see which drivers you have for SQL.
I have ODBC Driver 17 for SQL Server, SQL Server and SQL Server Native
Client 11.0
I prefer to use a connection string rather than DSN so that I don't have to
set up a DSN on each cl
I use SQLSTRINGCONNECT usually because those apps build the connection
string manually, but I do have another app that uses SQLCONNECT using a
defined DSN.
On 8/20/2019 12:26 PM, Peter Cushing wrote:
Hi,
Thanks to everyone that replied. I don't have to worry about getting
fired, so all good
Yes, agreed using stored procedures is a good way, however I believe you
still need SPT or CursorAdapters to access those stored procedures, so
they are not necessarily mutually exclusive.
Frank.
Frank Cazabon
On 20/08/2019 09:42 AM, Stephen Russell wrote:
Considering they are flipping over
Hi,
Thanks to everyone that replied. I don't have to worry about getting
fired, so all good there.
SPT seems the easiest to begin with, but not got it working yet.
I have created an ODBC link called X2live. I set it up as a system DSN
as I tried a user DSN first and that didn't work.
Just wonder
On 8/20/2019 11:15 AM, Stephen Russell wrote:
The initial request said that there was a plan already defined.
After running my app (VFP 9) on our local network (with a DBC) for many
years, we are upgrading it (in stages) to a visual studio app with SQL
server back end.
I would only work in prom
The initial request said that there was a plan already defined.
> After running my app (VFP 9) on our local network (with a DBC) for many
> years, we are upgrading it (in stages) to a visual studio app with SQL
> server back end.
I would only work in promoting future ways of doing things in this c
I'm with you mostly it would seem, Paul. I wrote my own SPT framework
years ago after watching Bob Lee demonstrate his VFP app in Wisconsin
accessing a MySQL database over the internet in New York back at
WhilFest in 2002 or 2003. CursorAdapters sounded great and I'm told
they work great toda
On 8/20/2019 9:42 AM, Stephen Russell wrote:
Considering they are flipping over SQL Server I would learn to USE SQL
SERVER correctly on the front end from VFP. You create the sprocs that do
all of your CRUD operations. Populate them from the fox world and as VFP
is replaced, the newer interface
Cursoradapter eases the transition from DBC to SQL: you can tailor the SQL
command according to the backend, recycle your code, test against either
backend seamlessly.
Thierry Nivelet
http://foxincloud.com/
Give your VFP app a second life in your cloud
> Le 20 août 2019 à 16:11, Paul H. Tarver
Peter,
Personally, I like SPT because I can build valid and safe pass-through commands
in my code based on user selections, generate the string, hand it off to the
server with an ASYNCH connection and easily provide users with progress
feedback while data is returned.
For some reason, I've n
Considering they are flipping over SQL Server I would learn to USE SQL
SERVER correctly on the front end from VFP. You create the sprocs that do
all of your CRUD operations. Populate them from the fox world and as VFP
is replaced, the newer interfaces will use the same sprocs you laid down
today
I use Visual MaxFrame Professional so the details are hidden from me and
I don't really care what technology is used behind the scenes. < smile >
I actually think that Drew coded it so that it works through remote
views in the background.
If I were to start doing my own code/framework now in
Richard Kaye wrote:
> Sure, Vince. I got bitten by the default behavior of SQLDISCONNECT(). In the
> DESTROY method of one of my forms was this little gem:
>
> SQLDISCONNECT(thisform.nHandle1)
>
> The problem is, if the user never hit the process that established that
> handle, it's default val
Thanks, Michael. In this case, the app is running on a LAN and was not
architected to use disconnected data.
Richard Kaye
Using disconnected datasets (instead of remote views), I always check
___
Post Messages to: ProFox@leafe.com
Subscription Mainte
NNECT() and it closes *all* open
handles. Oops.
Richard Kaye
-Original Message-
From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On
Behalf Of Vince Teachout
Sent: Wednesday, April 01, 2009 9:09 AM
To: profoxt...@leafe.com
Subject: Re: SQL Server connection hand
Richard Kaye wrote:
> I've got a user at one location reporting this error periodically. The
app gets its handle on startup and does not disconnect until it exits;
at least as far as code is concerned. The connection info is read from a
connection that lives in a common DBC. As far as its propertie
On Apr 1, 2009, at 7:55 AM, Richard Kaye wrote:
> figure out the answer shortly after hitting the send button
The Magic Send Button strikes again!
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/prof
Richard Kaye wrote:
> As always, post a message and figure out the answer shortly after hitting the
> send button. Found some code...
>
> Go back to your business. Nothing to see here...
As always, please post the answer, since you asked the question, so that
others in the same boat can benefit
As always, post a message and figure out the answer shortly after hitting the
send button. Found some code...
Go back to your business. Nothing to see here...
Richard Kaye
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.
Alan Bourke <> wrote:
> Stephen the Cook wrote:
>> I'm sorry but this advise is poor for any system. From the SQL2000
>> days and now in the more secure SQL2005 days security within the
>> domain is what you want to use. Sure you can use straight SQL Auth,
>> but it's a RPITA when you ever change
Judith Barer <> wrote:
> When connection to SQL server is using Windows authentification just
> as secure as using sql server authentification? What are the
> advantages of each one?
Ease of admin for one.
You can establish rights by GROUP instead of the person. So a few
contractors come in,
Use Domain groups on the SQL server. Then you are only maintaining the
groups in active directory not individual accounts.
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of th
Stephen the Cook wrote:
> I'm sorry but this advise is poor for any system. From the SQL2000 days and
> now in the more secure SQL2005 days security within the domain is what you
> want to use. Sure you can use straight SQL Auth, but it's a RPITA when you
> ever change servers. B
If people were
Judith Barer <> wrote:
If you want a quick overview on what and how to set yourself up you can call
me at the # below. I'll quickly go over the major points quickly, say a
about a half hours time.
Stephen Russell
DBA / .Net Developer
Memphis TN 38115
901.246-0159
"A good way to judge people
Judith Barer <> wrote:
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Alan Bourke
> Sent: Monday, February 26, 2007 11:48 AM
> To: [EMAIL PROTECTED]
> Subject: Re: sql server connection
>
> Judith Barer wrote:
&g
Derek Kalweit <> wrote:
> Yes-- windows authentication needs a valid windows account. Accessing
> locally, that can be a local account-- in a network environment, that
> must be a domain account, an account on a trusted domain, etc.
>
> Simply put, windows authentication is usually a pain in t
> > So I would assume that if you want to connect from a web site you should
> > use sql auth because you do not want to assume the user is using
> > windows.
> Well, you could set up a special user on the Windows side that just has
> access to the relevant SQL data, can't log on to a desktop sess
Judith Barer wrote:
>
> So I would assume that if you want to connect from a web site you should
> use sql auth because you do not want to assume the user is using
> windows.
Well, you could set up a special user on the Windows side that just has
access to the relevant SQL data, can't log on to a
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Alan Bourke
Sent: Monday, February 26, 2007 11:48 AM
To: [EMAIL PROTECTED]
Subject: Re: sql server connection
Judith Barer wrote:
> When connection to SQL server is using Windows authentification just
> > When connection to SQL server is using Windows authentification just as
> > secure as using sql server authentification? What are the advantages of
> > each one?
> With Windows auth you need to have a valid domain login already set up,
> with SQL auth you just need a username and password.
Y
Judith Barer wrote:
> When connection to SQL server is using Windows authentification just as
> secure as using sql server authentification? What are the advantages of
> each one?
>
>
With Windows auth you need to have a valid domain login already set up,
with SQL auth you just need a usernam
46 matches
Mail list logo
