Connect to external .mdb
Thank you for taking the time to report an issue.
What's wrong... Please write below.
I have an automated function to import external Access tables to my database (there is only ever 1 table in the external ACCDB/MDB), BUT the names of the external tables are different.
How can I import a table without specifying the name? (ie default import the only table abvailable)
DoCmd.TransferDatabase acImport, "Microsoft Access", Me!_txtPath, acTable, TableName, "tbl_MyTable", False
I have a mdb that has only tables
I have a 2nd mdb that links to these tables and also has all the queries, forms,
Can I modify the 2nd mdb to:
2. Not allow them to view the tables, forms, queries, macros etc.
3. Can I remove the Ribbon.and all tools including the Home, Create, External Data, Database Tools, and Acrobat
Where their only option to click will be within the forms I create?
At this stage pretty much all I know is that there is a DLL file that will create .TXT files that my database would then be able to read and convert into usable data.
Has anyone any experience or knowledge in this area?
e.g. VB code to pass commands to the external hardware (using/via the DLL perhaps) and calling/creating the required TXT files
Public Enum EnvironmentStatus
ProductionEnvironment End Enum Global Const g_EnvironmentStatus As EnvironmentStatus = DevelopmentEnvironment Sub ConnectTables()
Dim db As DAO.Database, t As DAO.TableDef
Set db = CurrentDb
For Each t In db.TableDefs
If InStr(1, t.Connect, "CB.mdb") 0 Then
Select Case g_EnvironmentStatus
t.Connect = ";DATABASE=P:\DatabaseDevelopment\CB.mdb"
t.Connect = ";DATABASE=P:\CB_Live\CB.mdb"
t.Connect = ";DATABASE=P:\DatabaseTesting\CB.mdb"
The files that are on the database are in a .mdb file format which is what access uses.
Currently I can connect to the ftp server and view the .mdb files using a cruddy third party vendor software that has no options for reports or sorting (which happens to be why i need to figure out how to connect to the server with Access).
I know all of the information such as the ip address, username, password, port etc.... that is required to connect.... i just dont know "how to connect" using Access. Any help would be appreciated.
In my environment, I am using Access Viewer only
These numbers represent text 'value1', 'value2','value3'
Is it possible tot connect these text to the value from the excel sheet (table in access)
(the sheet is a dumpfile from another system, and I dont wont to change the values in excel, only in mdb, preferably by a query
mdb file, the NAVIGATION form comes up and they can goto where they need to go. The problem were having is if user A, opens the .mdb file it is always trying to connect with exclusive access.
If no one else is in the app when user A opens it, she is able to but then if user B or user C and so forth tries to open it when user A was the first one to open it, they are locked out.
Now, if user B opens it first users C and so forth can get in with no problem, but User A gets messages that she doesn't have exclusive rights and any changes if made could be lost.
What I can't figure out is why User A keeps trying to connect exclusively when she is not even the user that created the applicationand when user A tries to open it, how do I change her to open it with shared access.
However, I would like to create and adapt these specifications using VBA and am not sure how to handle this. Are there (maybe?) internal/system tables that handle these specifications? And is it possible to access these programmatically?
Many thanks for any tips/links/howtos that you can give me.
Cologne and Bonn
When I open the ODBC data Source administrator and double click on the Microsoft Access Driver, I get the following error message: Microsoft ODBC Administrator. The Setup routines for the Microsoft Access Driver (*.mdb, *.accdb) ODBC driver could not be found. Please re-install the driver.
When I then click OK, I get the following error message: Driver's ConfigDSN, ConfigDriver, or ConfigTranslator Failed. The Specified DSN contains an architecture mismatch between the Driver and Application.