MDB linked to accdb?

[YouMust]

Good afternoon,

we have a database in accdb but I'm trying to connect to the database with labview to insert test results into the database and pull barcodes from.
unfortunately the mix of windows 64bit and office 32bit means the UDL doesnt work.

however it does work if I use MDB.

so could i make a blank MDB database and just link all the required tables from the accdb database?
The MDB will need to read/write to the accdb database.

thanks for any help offered!

 

[The_Doc_Man]

the mix of windows 64bit and office 32bit means the UDL doesnt work

Unless you were describing something incorrectly, this DOES work. In my office we used Win 7/64 bit and Office 2013/32 bit together without errors popping up because of the configuration. (We won't talk about the errors that popped up because I couldn't type...)

I think that to use an .AccDB back-end, you MUST use a version of Access that understands .AccDB files. I don't know that I have ever tried to have an old format of FE file with a new format of BE file, so I'm not sure. I know that Access 2013 correctly talked to a BE file originally created in Ac 2003 and that worked correctly.

Is "labview" a 3rd-party product name? We would need to know more about it before we could tell you what you could do with it.

 

[YouMust]

It's appears to be working, I made a blank mdb database opened it and linked the tables from the accdb.
All the tables imported.

Making an accdb then changing the extension to mdb is correct, I didn't see the option to change to mdb when saving.

Strangely the connection from labview to the database does work on my pc. But not on the test bench which has labview installed.

Labview is a piece of software that allows you to program i/o's to do a number of things, it also has a connectivity kit that uses .udl and Microsoft OLE DB provider for OCBC drivers to connect to databases

 

[sneuberg]

Making an accdb then changing the extension to mdb is correct, I didn't see the option to change to mdb when saving.

I don't thing changing the extension from accdb to mdb changes it to an mdb database but then maybe there's no difference if it's just backend tables. On the other hand if the tables had data macros I suspect they would be removed. In Access 2013 you get two option to save a database as mdb (see circled below). What version of Access do you have?

I tested saving an accdb backend as an Access 2000 database (mdb), relinked the accdb frontend to this backend and it worked.

 

[YouMust]

great thanks guys and yes you are correct it does work!!

but for some reason if i made a database on my pc then the UDL would not work/link, if however i made the database on the target machine then import my database then rename it to the oring and replace it on the network drive it works fine?? how odd.

theres no user permissions set on the file.

but anyway it is connecting to the database and it was some sort of corruption?

 

[CJ_London]

I don't thing change the extension from accdb to mdb changes it to an mdb database

it doesn't - mdb uses JET, accdb uses ACE. Aside from data macros (and multivalue and calculated fields), there are other differences - rich text for example in mdb is rtf and in accdb is html

 

[YouMust]

ok heres an update,

after importing the data across to a new data base some of the tables got messed up, as just one example. SerialNo got replaced with ID.

if i have a new database on the local drive with all its tables linked to the database on the networked drive. they would be updated automatically, what i mean is i dont have to run access. so when labview writes to the local db it will in fact write to the networked db?

I hope i made that clear
sorry for the noobish questions im trying to learn labview atm as well

 

[CJ_London]

so when labview writes to the local db it will in fact write to the networked db?

if you are asking if labview is writing to linked tables in an .accdb on your local drive (i.e. a front end) it will update the tables the .accdb is linked to on the network drive (i.e. a back end) then yes it will (that is basically a standard multiuser setup for Access), but the user that is using/hosting labview will need read/write access to the network location as well otherwise the 'link' cannot see the network file.

 

[YouMust]

thanks CJ that was what i was asking.

 

[YouMust]

well that didnt work, I linked to databases

But when labview tries to pull data from it, i get an error labview could not open f:\database\infosys.accdb

but my UDL points to a linked database at c:\database\infosys_ATE.accdb
I guess labview is looking past the linked database and reporting the f:\ accdb is faulty

 

[CJ_London]

going back to your original question

so could i make a blank MDB database and just link all the required tables from the accdb database?

the answer is no. You can link a .accdb database to a .mdb but not the other way round

sounds like labview will only work with a .mdb.

Or - labview does not have read/write access to f:\database\infosys.accdb

try using a udf rather than a mapped drive number

 

[sneuberg]

This Web page implies an .accdb database would work. Have you tried to recreate the UDL as describe in that page?

 

[YouMust]

thanks sneuberg,

I have done this, curiously that method does not work, NI have another guide which i cant find now :/ about using the create data link in labview this opens the same dialog box and makes the same UDL and works how odd.


my issue now however is that in the UDL dialog you can test the connection.
it says my database is of an unrecognized format.
if i make a new database and import all data from my old database it works?
indicating a fault/corruption in the original file?

is there away to check the integrity of the database?

 

[sneuberg]

thanks sneuberg,
if i make a new database and import all data from my old database it works?

Doesn't that solve your problem?

is there away to check the integrity of the database?

Compact and Repair is the only way I know of

 

[YouMust]

yes it does solve the problem

I'm concerned as to why it was in that 'state' and what the problem is that caused it. but I may well never find out.

But i'm very thankful of the help I've received!

I'll take a look at that function you mentioned