Jump to content


Photo
- - - - -

366- SQL ERROR


8 replies to this topic

#1 llony

llony

    Member

  • Members
  • PipPip
  • 25 posts
  • Gender:Male

Posted 22 September 2000 - 02:58 PM

I'm working with Sql server v7.0.
I've set a valid database name and password
and I've create a simple table with data on it
the external file type=SQLSERVE.
But when i try give maintenance to the file
i get a 366-sql error (Not a valid Database name or not drivers especifyed)
May anyone explain me what should i do to fix this error
or tell me step by step How to maintenance a sql table using proiv?

Help will be appreciate.

#2 Guest_clifcarr_*

Guest_clifcarr_*
  • Guests

Posted 22 September 2000 - 03:40 PM

This is the [ENVIRONMENT]part and below of ur Pro4.ini file in the c:winnt directory - all u
would have to do is change the ORACLE to SQLSERVE and change
the DLL filename(change PROORA815.DLL to the SQL Server DLL -
search the Pro4 directory) - (assuming u have installed
pro4 to the F:drive) - preferably have ur SQL server
installation on the same machine as the Pro4 installation.

[ENVIRONMENT]
FILETYPE=ORACLE
PROPATH=f:\pro40\BOOTS
PRODATA=f:\pro40\data
PRORUNTYPE=DEV
GUI=Y
PROTERM=GUICLR
STARTCLIENT=f:\PRO40\PROGUI.EXE /INI:f:\PRO40\LOOPBACK.INI
FSIDEFAULT=Btrieve
ORACLE_DLLNAME=f:\PRO40\PROORA815.DLL
SQL_SELECT_FOR_UPDATE=TRUE
SQL_CURSORS=32
ORACLE_SELECT_FOR_UPDATE=TRUE
[Database - SQLDEFAULT]
SQL_SELECT_FOR_UPDATE=TRUE
SQL_DBTYPE=ORACLE
SQL_FILETYPE=ORACLE
FILETYPE=ORACLE
CONNECTION=username/password@databaseservername
[CLIENT32]
INSTALLDIR=f:\PRO40
Command1=PROIV.EXE


#3 llony

llony

    Member

  • Members
  • PipPip
  • 25 posts
  • Gender:Male

Posted 22 September 2000 - 10:34 PM

Thanks, Clifcarr.
I didn't find any sql server dll at pro4.6 directory.
May you send them to me, please. I think the release available at proiv downloads do not include them.

#4 Guest_clifcarr_*

Guest_clifcarr_*
  • Guests

Posted 26 September 2000 - 11:25 PM

I checked the install - I dont think it has a SQL server DLL
Just change the FILETYPE under [DATABASE] to SQLSERVE and
remove any other information about Oracle or DB2.
Let me know if it works - I will try getting a copy of
SQL Server tomorrow and testing it out !

#5 llony

llony

    Member

  • Members
  • PipPip
  • 25 posts
  • Gender:Male

Posted 29 September 2000 - 09:31 PM

I've changed FILETYPE to SQLSERVE under [DATABASE]
and ALL is unchanged. What may i do?

#6 Guest_AJardim_*

Guest_AJardim_*
  • Guests

Posted 10 November 2000 - 07:21 PM

Llony -

Before you can get your SQLServer access working, you need to do the following:

Control Panel -> ODBC Data sources -> Create a System Data source,
that connects to your SQLServer database.

Name it: TESTDB (for illustration purposes)

Now, in the [ENVIRONMENT] section do the following:

SQL_DBNAME=TESTDB

[Database - SQLDEFAULT]
FILETYPE=SQLSERVE
PRODB_CHARSET=7
CONNECTION={username}/{password} (validated for the connection created above)

Now, in the ProIV file defs, your file definition should have the external type 'SQLSERVE'

You don't need to mess about with DLL names (the actual DLL is ..System32sqlsrv32.dll, but this is accessed through ODBC).

The limitation is that you cannot access multiple databases, which ideally, is what you want on a SQLServer/NT configuration.

Regards,
A. Jardim

#7 llony

llony

    Member

  • Members
  • PipPip
  • 25 posts
  • Gender:Male

Posted 29 November 2000 - 01:59 PM

I've already configure the ODBC and Pro4.ini. But when I try
to access a single table the same 366-SQL ERROR (Data Source
Name not Found and no default drives specified) occurs.

Thank you for your post.

#8 Guest_AJardim_*

Guest_AJardim_*
  • Guests

Posted 29 November 2000 - 09:53 PM

Llony -

Did you install the ProIV as a 'server' or 'workstation' version?

You must install it as a 'server' version and select SQLServer as a supported database.

Outside of that, I cannot recommend anything else - this does work for me on both NT/98.

Good luck,

Regards,
A. Jardim

#9 Ralph Gadsby

Ralph Gadsby

    Expert

  • Members
  • PipPipPipPip
  • 154 posts
  • Gender:Male
  • Location:United Kingdom

Posted 30 November 2000 - 12:23 PM

You must have an SQL_DBNAME entry in the [ENVIRONMENT] section of the pro4.ini file. The name specified on this entry must be the same as an entry specified in the System DSN section of the ODBC datasource administrator. The message that you are getting indicates that this is not the case.



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users