I am developing a Windows Forms application which is required to connect to Sage 100 and get order information. I am using ASP.NET and SQL Server 2008.
Is there a way to connect to the sage 100 database?
If you've installed the ODBC driver that came with Sage 100, you can get a provider string by adding a System DSN in your ODBC Data Source Administrator (Start Menu -> Administrative Tools -> Data Sources (ODBC)).
Click the System DSN tab, then Add... On the Basic tab, Give the DS a name and description, then enter the database directory. Just as the dialog box says, it should be the directory that contains your PROVIDEX.DDF file in your Sage 100 installation.
On the Logon tab, enter the company code, user ID and password for the company you want to access.
On the Options tab, enter the following in the Prefix for data files box:
<Sage 100 ERP directory>\SY\, <Sage 100 ERP directory>\==\
Enter the following in the Path to Views DLL box:
<Sage 100 ERP directory>\Home
Obviously on both of those, you want to use your actual Sage 100 ERP directory.
Check Dirty Read, Burst mode and Strip trailing spaces.
Then, on the Debug tab, test your connection. If it works, click Connection String and copy the connection string.
Next, in SSMS, add a new Linked Server. Enter a Linked server name, choose Microsoft OLE DB Provider for ODBC Drivers from the dropdown list, enter a Product name (doesn't matter what you put there) and paste the connection string in the Provider String box. Hit OK and the new Linked Server should appear. Now, you can create Views in your app database to access the Linked Server and use those views just like data tables.
Related
I am using the NSIS nsODBC plugin to create an systemdsn entry.
When I call the command as shown below it works and creates my system dsn odbc.
nsODBC::AddSysDSN "ODBC Driver 11 for SQL Server" "DSN=test" "server=localhost" "DATABASE=test" "Trusted_Connection=Yes"
Pop $0
Pop $0 Returns "Successful" and in my ODBC Data Source Administrator I see my connection and it works.
But I need to create my system dsn with a username and password, on the forums and site I have seen they say it should look like the following:
nsODBC::AddSysDSN "ODBC Driver 11 for SQL Server" "DSN=test" "server=test" "DATABASE=test" "UID=test" "PWD=test"
Pop $0
When I run this command Pop $0 returns the text "error" and no system dsn is created.
I have checked the SQL server instance it has the test database, a login account called test which is a system admin account, it is in mixed mode authentication.
Any suggestions as to what I am doing wrong as to why it will not create a system dsn with a username and password?
Thanks in advance
Andy
That plug-in is badly designed because it uses everything on the stack as its parameters. It is also a very thin wrapper around the database API so as long as your stack is empty before calling then the problem is most likely a missing/wrong parameter and not a bug in the plug-in.
Calling the plugin with parameters like "foo=1" "bar=baz" is "translated" to foo=1\0bar=baz\0\0 which is what you see on MSDN and that is the C/C++ syntax for a double null terminated key-pair string.
Why is Server set to test and not localhost?
The code listed on the MSDN page for ConfigDSN says:
For example, to configure a data source that requires a user ID, password, and database name, a setup application might pass the following keyword-value pairs:
DSN=Personnel Data\0UID=Smith\0PWD=Sesame\0DATABASE=Personnel\0\0
Maybe the pair order matters, I don't know.
as you know, the database connection parameters are listed in Web.Config which it's text, now the app is hosted in Windows, I want to apply follwoing:
1- exe file by clicking it should ask for the following
a -> database server host address
b -> database server sql user name
c -> database server sql database
d -> database server sql user password
after all the parameters are correct it should allow to store the connection and I will address the connection in webconfig(connection file) is for sure encrypted and it's show only encrypt the server detail(iis server) which even if some one copy the app folder to another server it should not work
--> here I know how to encrypt only in single file but the problem is for developing such exe which should check the detail connection if it's success and by server-IIS detail
where I should start, help of experts saves our time , best wishes
I went trough this answer but could not solve.
I have a 2010 Microsoft Access database in the format FixList.accdb
There is one table and one form in it, that i want a small number of users to access at the same time.
I have split the database, so that the back end is in a different folder to the front end.
Finally, i have gone to options and selected the following:
- Default Open Mode =Shared
- Default Record Locking = No locks
- Open Databases by using record-level locking (NOT ticked)
It opens fine when 1 user opens the database, but when a second user double clicks the Access file to open, the following message appears. "You do not have exclusive access to the database at this time. If you proceed to make changes, you may not be able to save them later". My question is, what other change(s) can i make to this database so that the error message above does not appear when more than one person opens the file?
Do NOT have more than one concurrent user open the same copy of the front-end (e.g., by having all users open the copy from a folder on the server). Each user must have their own local copy of the front-end .accdb/.accde file.
I am developing a transformation (on pentaho 4.4.0) which basically reads data from one oracle DB (11g), makes some transformation and loads data into another Oracle DB. Now for DB table input/output when I need to select a connection I have to select it from a drop down menu in 'Edit Step'. When I edit the connection, it asks me settings, like Host name, database name, port number, user name, password.
What I want is, to create a text file called 'Pentaho_connection_properties' in some directory on my machine where I will save all these info and as soon as I choose a connection name from the connection drop down menu, Pentaho should automatically read the file and populate the settings corresponding to that connection name. The purpose is to get rid of this manual process to entering settings again and again for multiple use of same DB.
Please let me know how this can be done. I will appreciate if you can be little explicit since I am new to Pentaho.
Thanks
Switch to using database repositories. Connection definitions are shared throughout an entire database repository.
I'm trying to set up an ODBC client driver for Progress 10.1b. I was able to install the client software that is required, but there is apparently also an ODBC.reg script file that needs to be run to correctly set up the registry in order for me to use the ODBC drivers.
Can anyone point me to where I would find this script? Or tell me the set of registry entries that would have to be made?
That's not a standard part of the install process.
Are these the steps that you followed to get the client installed?
If, as you say, the client was properly installed you just need to setup the DSN. The following should work (stolen and lightly edited from the Progress Knowledge Center):
Start up the ODBC Data Source Administrator(found in Control Panel within the Administrative Tools folder)
Example:
1. Select the System DSN tab
2. Select the Add button to the right
3. Select the MERANT 32-BIT Progress SQL-92 driver for your version of Progress.
4. Select Finish
That brings up the configuration screen for a new DSN.
Fill-in the following information:
1. Data Source Name..... (whatever you choose)
2. Description.......(optional and whatever you think is appropriate)
3. Host Name......(the server where the database is located)
4. Port Number.... (the port your database broker was started with...if multiple
brokers..the SQL broker port)
5. Database Name....(database name you wish to connect to)
6. User ID...(the user you logged in with or if security is turned on..a user
that can connect to the database)
7. Leave all other tab settings at the defaults for the initial configuration.
8. Select the Apply button.
9. Select the Test Connect button.
10. Screen requesting a password pops up. (enter one only if the database
normally requires a user name and password from the 4GL side to enter the database)