Recent content by nmtexman

You're preaching to choir on that. Unfortunately "The Powers That Be" have decided that we will upgrade to W2K.

The db contains telephone numbers for everyone in the complex. I don't know how many people log on at the same time, but it is read-only logon. Only the admin types (20 + me) can do writes. It works quite well for us now that we have gone to ADODB for connectivity.

Under Windows 2000/Access 2000 the date() function is no longer supported. You'll have to find another way to get the date in there, you can no longer set the date field in a table to date(). Also no longer supported is the Null default value.

I think the back end/front end connection will work well with you. We have a telephone number Access db here which everyone in the complex has access to (700+ people). We also have admin type access to the same tables which is limited to about 20 people. The front ends are the two different...

Thanks for all the help on this one. We finally decided to disconnect the table from any forms, etc. So far, no one has missed it.

When we attempt to open the databases, we get the "You do not have permission to open this database" message. Our superuser has granted us all the permissions she can, but still no luck. Since we can't even open them, we can't look at the forms. We have tried renaming copies to the...

We have access to the directory where the databases are stored. We are set up in the WorkGroups for those databases. We cannot even look at the databases. We have not been asked for passwords. Security seems to be at NT level and DB level.

We are currently in the middle of converting 16-bit Access .mdb's to Access 2000. We have come across several databases where the administrator's have moved on to new positions and no one can access them to upgrade them to A2K. Does anyone know of any methods where we can circumvent the...

Once you have given the commands to move the mouse pointer to the area you want it to go to, the Call Command1_Click will click the mouse at that location, as dragnut indicated.

I am trying to convert an ODBC VB4 program to ADODB. I have set it up in the following manner: Public mdbPICS as ADODB.Connection Public gsConnect as String Dim lsServer as String * 255 gsConnect = "Provider=sqloledb.1" & _ ";PWD=" & gsPASSWORD &...

Good luck. Don't turn over your canoe. Our Governer flipped his kayak recently. Big stink. Bob

You think you have a problem now, wait until you go to Windows 2000 (2k). Windows NT is a 32-bit system. Access 2 (or is 2.2) is 16-bit. There are some inherant problems with that combination and Windows NT4 is supposedly able to handle that difference. It may be that you are missing a...

Not being familiar with SQL Anywhere as such, I can only suggest you get a "evaluation" copy and see if that helps. If not, it will be almost impossible to access the data without some serious de-compiling work.

The References window refers to object libraries available to you. An object file is a file with an .olb extension. There are five objects that need to be referenced (checked) for use with Access. These are Visual Basic for Applications, Microsoft Access 9.0 Object Library, Ole Automation...

Good luck. Bob