|
-
Dec 9th, 2001, 04:23 AM
#1
Thread Starter
Junior Member
RDO - Tables and Fields
Does any one have a nice piece of code for creating Tables and Fields using RDO methodology?
I know DAO or ADO is better, but unfortuately I have to use RDO.
Can any body please help????!!!!!
-
Dec 10th, 2001, 04:02 PM
#2
Re: RDO - Tables and Fields
Originally posted by djrmkr
Does any one have a nice piece of code for creating Tables and Fields using RDO methodology?
I know DAO or ADO is better, but unfortuately I have to use RDO.
Can any body please help????!!!!!
what database engine are you using?
-
Dec 10th, 2001, 04:23 PM
#3
Thread Starter
Junior Member
I'm using an msaccess97 MDB. I'm using RDO references to access the data
eg.
myconnection.rdocolums("ID") = MYID
I need to create some new tables and feilds so I can add some new functionality to my program. But I don't want the user to create the tables and feilds themselves. (to higher risk of them stuffing it up)
I don't want to add another file (system.mdw) to the list of files installed with the software.
P.S (I'm planning on upgrading it to SQL server, which means I can then use the ADO references, Problem solved, but for now I'm stuck with RDO.
-
Dec 10th, 2001, 05:28 PM
#4
Originally posted by djrmkr
I'm using an msaccess97 MDB. I'm using RDO references to access the data
eg.
myconnection.rdocolums("ID") = MYID
I need to create some new tables and feilds so I can add some new functionality to my program. But I don't want the user to create the tables and feilds themselves. (to higher risk of them stuffing it up)
I don't want to add another file (system.mdw) to the list of files installed with the software.
P.S (I'm planning on upgrading it to SQL server, which means I can then use the ADO references, Problem solved, but for now I'm stuck with RDO.
Stuck RDO?? Why not DAO?
-
Dec 10th, 2001, 05:41 PM
#5
Thread Starter
Junior Member
Including DAO, means another reference (Not a big issue), However I need to use the command
SystemDB.Engine = ???????????
And I don't know where the system.mdw file will be located on various machines.
It also doesn't regonise that fact the I want to change the path to the SystemDB to something like:
SystemDB.Path = App.Path & "\system.mdw"
Which is why I want to use RDO. I know there is a command in RDO that is similar to the DAO command, but uses the RDO connection methods.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|