Recent content by Arnold

I have to change the Power/Energy Saver/Energy Saver Mode BIOS setting from either "Minimal" or "Advanced" to "Disable". I need to do this on Compaq Deskpro workstations that are running NT 4.0. I know I can do it manually, but I have too many to have to go to...

I am upsizing my Access 2000 database to an Access 2000 Project and am unable to to bring my export specifications into the project. Also, the project won't allow me to save new import/export specifications. Any ideas?<br>Thanks,<br>Arnold

I have a SELECT statement in Access 2000 that contains the following:<br>Format([UnitPrice]/[Weight],'$0.0000') AS expr1<br><br>I am looking for an equivalent in SQL Server, but have yet to find it.&nbsp;&nbsp;The SELECT statement is the source for a ListBox in an Access 2000 Project.<br><br>Any...

I have a SELECT statement in Access 2000 that contains the following:<br>Format([UnitPrice]/[Weight],'$0.0000') AS expr1<br><br>I am looking for an equivalent in SQL Server, but have yet to find it.&nbsp;&nbsp;The SELECT statement is the source for a ListBox in an Access 2000 Project.<br><br>Any...

Elizabeth,<br> Thanks for your help.<br> <br> Yeah, I tried that. I cut the phaselist table down to only one field, the primary key field, and imported that. I still had the the same problems. I am currently recreating the table in sql server by hand, and then I will populate some of the...

I had a breakthough. I got the &quot;PartNumber&quot; table to update and delete without any problems at all. When I upsized to sql server, I imported the data at the same time. When I did this, I got an error when it tried to import the data. (The error was &quot;Server Error 206: Operand type...

calahans,<br> Thanks for your help!<br> <br> I don't think the problem is with permissions on the tables. The permissions are the same on all my tables in the database and I have no problems updating and accessing those tables. I can even update and delete certain records in the...

I have an Access 97 database that I am upgrading to utilize a SQL Server 7.0 backend and an Access 2000 front end. First, I am upsizing the Access 97 database to Access 2000 and then running the Upsizing Wizard to create the Access 2000 database with linked tables to the SQL Server. When I...

I have an Access 97 database that I am upgrading to utilize a SQL Server 7.0 backend and an Access 2000 front end. First, I am upsizing the Access 97 database to Access 2000 and then running the Upsizing Wizard to create the Access 2000 database with linked tables to the SQL Server. When I...

Thanks for the input, but I have already installed both SR-1 and SR-2 and they didn't fix the problem. Any more ideas? Thanks for the help.<br> <br> Arnold<br>

I have an Access 97 database that is made up of a front end and a back end, both in Access 97. Just the tables are in the backend. I then link the front end to the backend with linked tables. Next I make an MDE file out of the front end. I have about 10-15 concurrent users at any one time...

I found out what was wrong with my &quot;dbSeeChanges&quot; command, it goes after the &quot;dbOpendynaset&quot; command. They are both in the statement.<br> <br> I still haven't solved my &quot;Cannot group by a bit column&quot; problem yet. So if you could help me out with that one, that would...

I found out what was wrong with my &quot;dbSeeChanges&quot; command, it goes after the &quot;dbOpendynaset&quot; command. They are both in the statement.<br> <br> I still haven't solved my &quot;Cannot group by a bit column&quot; problem yet. So if you could help me out with that one, that...

I am trying to convert an Access 2000 database over to SQL 7.0, but I am having some problems. I ran the upsizing wizard to upsize the table structure and link the database tables to the sql 7.0 tables. That worked fine. I then imported all the data into the SQL 7.0 backend. Again no...

I am trying to convert an Access 2000 database over to SQL 7.0, but I am having some problems. I ran the upsizing wizard to upsize the table structure and link the database tables to the sql 7.0 tables. That worked fine. I then imported all the data into the SQL 7.0 backend. Again no...