My company had a very old one form module developed in VB and back end is Access and I was forced to remove that system and re install this application to new system
I had succeed in doing the same and Data entry etc is working fine the only issue is when I am trying to give the print a crystal report form is opening which gives the below message.
I installed Microsoft Access and the db file is also in the directory folder.Can any one sugest any solution please
Related
Every application I use to initiate an ODBC connection that I've created to my IBM Notes 9 DB results in getting an error during connect:
Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
I have scoured the web trying to correct this and have not been able to find an answer that solves for this issue on my machine. I am able to open and access the Lotus Notes DB within the Notes 9 software. I am able to create the ODBC System DSN and I know that it's connecting to the server properly because all of the available .nsf files populate in the "Database:" dropdown menu when going through the new ODBC connection setup. I am able to see my username which gets populated from my Notes ID file. The issue occurs when I use something to initiate the ODBC connection. I have tried Excel, QlikView, AQT, Teradata SQL Assistant all with the same result. Once I choose the ODBC connection that I've created, and click on "Ok" in each application I've attempted this with, I am met with the same error above.
I used Event Viewer per a suggestion in an older post online and received the message below:
Could not load NSQLE32.EXE. This file must exist in the same directory NSQL32.DLL and NSQLV32.DLL is in. It is possible NSQLE32.EXE could not be loaded because NotesSQL couldn't locate a valid Notes/Domino installation (couldn't find NNOTES.DLL) -- this may be because user (MYUSERID) does not have the correct rights to the Notes/Domino directory. It could also be because NotesSQL can not find your Notes/Domino installation in the Registry. NotesSQL looks for the NNOTES.DLL file by looking in the path pointed to by the following Registry entries -- HKEY_LOCAL_MACHINE\Software\Lotus\Notes{version}\Path : HKEY_LOCAL_MACHINE\Software\Lotus\Domino{version}\Path. If neither of these registry entries exist or they point to an invalid version of Notes/Domino NotesSQL will not work. To resolve -- please re-install Notes/Domino.
Some notes (no pun intended) and things I've done:
Verified that the DLLs mentioned in Event Viewer do exist in the proper directories.
Run the Nsql_ALM.exe application to configure the NotesSQL driver.
Used the 32-bit ODBC Administrator because my Notes 9 is 32 bit, as well as the driver. The 64 bit driver would not even allow installation (attempted this after hitting this roadblock) but the 32 bit installed successfully.
Modified my System Environment Variable for Path to include the true location to notes.ini, which resides in:
C:\Users\MYUSERID\AppData\Local\Lotus\Notes\Data
Modified my System Environment Variable for Path to include the location to the NotesSQL driver, which resides in:
C:\NotesSQL
Modified my registry to ensure that the appropriate strings exist to reference the proper files:
HKEY_CURRENT_USER\Software\Lotus\Notes\NotesIniPath (to notes.ini)
HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes\9.0\Path (to notes application)
HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Notes\9.0\DataPath (to notes.ini)
HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Domino\9.0\Path (to notes application)
HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Domino\9.0\DataPath (to notes.ini)
Set the NSQLE32.exe application to run in compatibility mode with all other options.
Attempted with everything run as administrator.
Uninstalled both Notes and NotesSQL and reinstalled everything cleanly again.
Attempted a log via Tracing within ODBC Administrator and it will not create a log file when I am attempting the connection. It will populate, however, with all of the system ODBC connections when the calling application attempts a lookup of the existing connections to populate in the dropdown menu. If I start tracing after the dropdown menu has been populated, then attempted the ODBC connection, even multiple times and with multiple versions, a new log file is never created.
I'm not sure where to go from here. Has anybody had this issue and is there something else that I can do in order to fix it?
I was able to correct the issue based on information in the Event Logs (Windows - Application) indicating that the Notes.INI file could not be located. I first added the location of notes.ini to the user and system environment variables, however, the issue persisted. I then moved notes.ini to the c:\NotesSQL folder where database connectivity dll's such as NSQL32.dll are found. This corrected the issue.
The application calling notes is SAP BusinessObjects Edge (Enterprise - Crystal Reports) 4.2 SP07.
notes.ini can not be found - Windows application event log
Let me lay out the background details first.
I'm using visual studio 2013 to write a vb.net windows forms application to load a crystal report (.rpt) file. The main report and sub report uses a SQL command from a Pervasive database (through an oledb connection) as shown in the picture below. For privacy, I've changed the database name to DBNAME.
I installed SAP Crystal Reports Runtime Redistributable 13.02 on the client computer. Obviously, I have the developer version on my computer.
Everything seems to work just fine when I run the build from my computer (the one used for developement), but when I try to run it on the client computer I get a window like the following:
So a few things to note here:
On the development computer, this prompt doesn't appear.
For some reason the database name shows up where the file server name should be
I never set a username or password, nor have I ever needed one to access this database through the control centre from any computer on
the network
no conceivable combinations of usernames and passwords work (including network credentials, windows credentials, and leaving it
blank)
I've tried forcing the credientials in the viewer form load event
CrystalReportViewer1.ReportSource = rpt
rpt.SetDatabaseLogon("", "", "FILESERVER", "DBNAME")
rpt.Subreports("Subreport2").SetDatabaseLogon("", "", "FILESERVER", "DBNAME")
rpt.Load()
but it doens't seem to make a difference. What am I missing?
Ok, I got it. Thanks to Bugs for pointing me in the right direction. The problem was with the connection type in the report. Changing the connection to ODBC (RDO) using 'right click > Database > set Datasource location' got rid of the credentials prompt, but instead caused a "Failed to open the connection" error. From there I looked for differences in the ODBC administrator from the pervasive control centre. I found that I had a system DSN that happened to have the same name as my database (which is why it confused me). Creating the DSN on the client computer resolved the connection problem.
I have an SSIS package that reads data from an Excel source and separates out into invalid data with a reason field or valid data if it passes all my validation checks (i.e. duplication checking, valid responses, etc.). The invalid and valid files are Excel destination files.
The package runs as expected on my old laptop connected to the network. I've had to change to a new laptop and worked with IT to install all the same SQL Server software. On the new machine, connected to the same network with the same login credentials in my data sources, the package does not run as expected.
I click debug and it looks like it's processing as normal and I receive the message, "Package execution completed. Click here to switch to design mode, or select Stop Debugging from the debug menu." I stop debugging and it looks like all rows were sent to the invalid Excel file as expected. But when I open the file, it's empty. The valid Excel file is also empty.
I'm wondering if there is a compatibility issue with the version of Microsoft Excel on this machine? This setup has MS Excel 2013 with some patch that allows accessing 2010 version files. The old setup had MS Excel 2010. I'm running SQL Server 2008 R2.
Any help is greatly appreciated.
Thanks,
Sisto
I have a small vb.net application using window forms with dataset. Currently the database is stored in c:\. When I created the MSI package and installed on another workstation, I need to change the database location to a network drive z:\, but my connection string in app config is already indicated C:\ hence resulted in error.
How can I solve this?
I've made VB.NET application in VS2010 that uses a 2007 Access database, called MenuDB.mdb. During development, everything was fine.
Now that I'm publishing it, I'm getting weird errors because for some reason the app isn't connecting to the database.
I install the application and run it but as soon as it opens it gives this error:
System.Data.OleDb.OleDbException (0x80004005): Could not find file
'C:\Users\Administrator\AppData\Local\Apps\2.0\Data\OV86PXJA.K3R\8575R5AY.95Z\menu..tion_0d4fa454d69e8e6b_0001.0000_8340d263807cbb71\Data\MenuDB.accdb'.
I know the problem has to do with the way I'm relating the application to the database, but I don't know which way is right. In Solution Explorer I changed the Build Type of MenuDB.accdb to "Content" (earlier it was embedded resource". But it doesn't work either way. In my App.config I have the following connection string:
connectionString="Provider=Microsoft.ACE.OLEDB.12.0;Data Source=|DataDirectory|\MenuDB.accdb"
I want that when I deploy the application, the database should just sit in the application folder, wherever it gets installed. How can I do that?
Edit
I don't mind deploying it in such a way that I need to paste the database somewhere myself on the target machine - as long as it works.
If you have multiple users using the same or similar database, and dont have access to a SQL server (MySQL, MSSQL, or others), then co-locate the database at a central location (preferably network location) that all the users will have access to and change the connection string to accomidate the database location being on the network.
Just let it be known, Access can handle up to 10users when doing simple data retrieval/submission but if you ever have it open while others are accessing via data objects, then you may lock them out.